What problem does it solve? Bug fixes often drift out of scope: developers (or AI assistants) sneak in refactors, skip verification, and leave no record of what was actually changed. This Skill enforces a disciplined fix workflow that only touches files declared in the confirmed analysis, verifies against the original reproduction steps, and archives a structured fix note. ## Core Features & Use Cases - Scoped Implementation: Only modifies files listed in the confirmed analysis plan; out-of-scope findings are logged as follow-up notes instead of being silently changed. - Dual Entry Paths: Supports a standard path (from a confirmed issue analysis) and a fast-track path (directly from an issue report with a stated root cause), both requiring explicit user confirmation before editing code. - Verification & Escalation: Runs a verification checklist (reproduction steps, expected behavior, regression on affected modules, browser checks for frontend changes) and escalates to log-based debugging when the fix does not work. - Fix-Note Archiving: Writes a {slug}-fix-note.md record with change lists, verification results, and leftover items, then guides scoped commits. - Use Case: After an issue analysis confirms that a null check is missing in serial/parser.ts:42, use this Skill to apply exactly that fix, re-run the reproduction steps, and archive the fix note without touching unrelated code. ## Quick Start Tell the AI to start fixing the bug according to the confirmed analysis plan and record the fix note when verification passes.
