dylan-dog

Runs premortem risk analysis on specs and adversarial two-pass review on code diffs.

1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/dariovr1/sixth-sense --skill dylan-dog-dariovr1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dylan-dog
Source: https://github.com/dariovr1/sixth-sense/tree/main/skills/dylan-dog
Command: npx skills add https://github.com/dariovr1/sixth-sense --skill dylan-dog-dariovr1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews and spec approvals often miss edge cases, failure modes, and design risks because they rely on a single shallow pass. This Skill systematically hunts for bugs and failure modes before they ship, using structured heuristics instead of gut feel. ## Core Features & Use Cases - Premortem Mode: Analyzes a spec or design before implementation by imagining the feature has already failed, then mapping causes to probability, impact, and mitigations written directly into the spec. - Hunting Mode: Reviews code diffs with a two-pass approach — a triage agent classifies sections by risk, then a hunter agent performs deep adversarial analysis only on high-risk sections, saving tokens. - Shared Heuristic Checklist: Applies systematic categories (SFDIPOT, CRUD, boundary analysis, concurrency, security, mutation thinking, dependency legitimacy, and more) to both modes. - Use Case: Before approving a new payment-flow spec, run a premortem to enumerate failure causes; later, when the implementation diff arrives, the review verifies that each promised mitigation actually exists in the code. ## Quick Start Invoke the skill with /investigate on a spec or code diff to run a premortem or adversarial review.

Frequently Asked Questions about dylan-dog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a premortem analysis on a software spec?

Invoke the skill on a written spec before final approval. It imagines the feature has already failed, enumerates plausible causes mapped to checklist categories, and assigns probability, impact, and mitigations written into the spec itself.

How does two-pass code review work on a diff?

A triage agent first classifies diff sections by risk level, then a hunter agent performs deep adversarial analysis only on the deep-flagged sections. Small diffs under roughly 150 lines skip triage and go straight to the hunter.

What heuristic categories does the review checklist cover?

The checklist covers SFDIPOT, CRUD completeness, boundary and equivalence cases, concurrency, failure recovery, security, mutation thinking, maintainability smells, performance regressions, accessibility, and dependency legitimacy.

When does the skill skip deep review of a diff?

Deep review is skipped when triage flags no deep sections, such as diffs containing only comments, renames, or tests. The skill then reports that shallow review is sufficient along with triage's rationale.

Why use two passes instead of multi-round agent debate?

Multi-round debate increases accuracy only marginally while scaling cost up to 90-100x. This skill uses at most two sequential passes, triage then hunter, never an iterative debate between agents.