Skill 5 of 6 · Remediate
deep-bugfix
/deep-bugfix
Diagnosis-first remediation: find the real cause, fix it once, prove the bug is gone - and make sure nothing around it broke.
What it does for you
No more "fixed" bugs that come right back
Feed it triaged review findings, a pasted bug report or stack trace, or a failing test - it treats them all the same way: diagnose first.
Root causes, not symptom patches
The reported explanation is treated as a hypothesis, not a spec. deep-bugfix re-diagnoses independently and fixes minimally at the confirmed cause.
One fix closes the family
Findings that share a cause are clustered and fixed together - six symptoms can collapse into one fix, and no sibling gets silently left behind.
The fixer never grades itself
A separate fresh agent tries to refute the claim that the bug is fixed - tracing the corrected behavior step by step. Nothing unproven ever ships.
Blast radius contained
Everything that depends on the changed code is re-tested before commit - because the real danger in bug-fixing is breaking what relied on the old behavior.
The non-negotiable order
Prove before commit
Per fix, the sequence never changes: apply → prove the bug is gone → confirm nothing broke → commit. Two of the three proof verdicts short-circuit the commit entirely.
A regression reverts immediately. If the adversarial proof can't confirm the fix, it gets one more diagnosis attempt - then the changes are reverted and you get a structured report instead of a quiet mess in your working tree.
Where it fits
Closing the review → fix → re-review loop
Review finds it, you accept it, deep-bugfix proves it gone - then the docs catch up.