Focused fix
Agent skills, autonomous agents, and MCP-companions for programming
npx -y skills add DROOdotFOO/agent-skills --skill focused-fixAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Structured 5-phase bug fix methodology with root cause verification. TRIGGER when: user wants to fix a bug, debug an issue, investigate a failure, or says "focused fix". Also when a fix attempt has failed and the user wants a systematic approach. DO NOT TRIGGER when: user wants architecture analysis (use architect), QA triage (use qa), or code review (use code-review).
SKILL.md
2.4 KB, as published. Nobody here has run it
focused-fix
Structured 5-phase bug fix methodology. No shortcuts.
The Iron Law
NO FIXES WITHOUT COMPLETING SCOPE -> TRACE -> DIAGNOSE FIRST.
If you jump to a fix before completing the first three phases, you will:
- Fix symptoms, not causes
- Break something downstream
- Waste more time than you saved
5 Phases Overview
| Phase | Name | Purpose |
|---|---|---|
| 1 | SCOPE | Map the feature boundary -- what is this code supposed to do? |
| 2 | TRACE | Map all dependencies flowing in and out of the scoped area |
| 3 | DIAGNOSE | Systematically find every issue in the scoped area |
| 4 | FIX | Repair in strict order: deps -> types -> logic -> tests -> integration |
| 5 | VERIFY | All tests pass, including downstream consumers |
3-Strike Architecture Check
Before starting any fix, check if the bug reveals an architectural problem:
- Strike 1: Is this the same kind of bug you have fixed before in this codebase? If yes, the architecture is inviting this bug class.
- Strike 2: Would this bug be impossible if a dependency were inverted or an interface existed? If yes, note the architectural improvement.
- Strike 3: Does fixing this bug require changing more than 3 files? If yes, the feature boundary is wrong.
If any strike hits, note the architectural issue. Fix the bug first (do not refactor mid-fix), then file a follow-up issue for the architectural problem.
What You Get
- A verified bug fix produced through five sequential phases: scope, trace, diagnose, fix, verify.
- Root cause identification with an architectural strike assessment noting whether the bug class is systemic.
- All tests passing after the fix, including downstream consumers, with a follow-up issue filed for any architectural problems discovered.
Reading guide
| Working on | Read |
|---|---|
| Executing the 5 phases, risk labels, red flags, anti-patterns | five-phases |