What problem does it solve?
Fixing bugs often expands scope, lacks systematic verification, and leaves no clear archival record of what was changed and why. This Skill enforces narrow, scope-limited repairs based on an already-confirmed root cause, ensures reproducible verification, and records the closure so future maintainers can trace intent.
Core Features & Use Cases
- Scope enforcement: Only modify files declared by the confirmed analysis or the fast-track report, preventing "scope creep" during fixes.
- Stepwise verification: Provides a clear verification checklist (repro steps, expected behavior, impact smoke tests, frontend/browser checks, and test runs).
- Audit trail: Produces fix-note.md from templates and guides a scoped commit that bundles code changes and documentation for easy traceability.
- Use case: A developer uses this Skill after analysis.md confirms a root cause to apply the minimal code change, run the verification checklist, and archive the fix-note for the issue.
Quick Start
Ask the assistant to "Begin issue fix for <issue-directory> using the confirmed analysis, apply the scoped changes, run verification, and create fix-note.md."