Back to skills
Repair
Fix
/cf:fix
Adaptive, evidence-backed repair after diagnosis, from quick local fixes to bounded incident work.
Use When
- A root cause has been identified.
- A bug needs a safe cause-aligned repair.
- A production incident needs staged regression proof.
Flow
01 / Evidence
Start from a completed debug contract or diagnose first.
02 / Bound
For non-trivial work, state outcome, constraints, non-goals, and acceptance.
03 / Route
Use a direct repair or post-diagnosis research, brainstorm, and planning only when needed.
04 / Fix
Apply the real repair, not a symptom mask.
05 / Verify
Re-run reproduction, blast-radius checks, and prevention proof.
Output
A bounded repair with before/after proof and explicit residual risk.
Avoid
Do not use it for speculative refactors, feature work, or a symptom-only patch.
Next Handoff
/cf:test and /cf:code-review