focused-fix
Use when the user asks to fix, debug, or make a specific feature/module/area work end-to-end. Triggers: 'make X work', 'fix the Y feature', 'the Z module is broken', 'focus on [area]'. Not for quick single-bug fixes — this is for systematic deep-dive repair across all files and dependencies.
Profile →npx skills add alirezarezvani/claude-skills --skill focused-fix --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Focused Fix — Deep-Dive Feature Repair ## When to Use Activate when the user asks to fix, debug, or make a specific feature/module/area work. Key triggers: - "make X work" - "fix the Y feature" - "the Z module is broken" - "focus on [area]" - "this feature needs to work properly" This is NOT for quick single-bug fixes (use systematic-debugging for that). This is for when an entire feature or module needs systematic repair — tracing every dependency, reading logs, checking tests, mapping the full dependency graph. ```dot digraph when_to_use { "User reports feature broken" [shape=diamond]; "Single bug or symptom?" [shape=diamond]; "Use systematic-debugging" [shape=box]; "Entire feature/module needs repair?" [shape=diamond]; "Use focused-fix" [shape=box]; "Something else" [shape=box]; "User reports feature broken" -> "Single bug or symptom?"; "Single bug or symptom?" -> "Use systematic-debugging" [label="yes"]; "Single bug or symptom?" -> "Entire feature/module needs repair?" [label="no"]; "Entire feature/module needs repair?" -> "Use focused-fix" [label="yes"]; "Entire feature/module needs repair?" -> "Something else" [label="no"]; } ``` ## The Iron Law ``` NO FIXES WITHOUT COMPLET
- When to Use
- The Iron Law
- Protocol — STRICTLY follow these 5 phases IN ORDER
- Phase 1: SCOPE — Map the Feature Boundary
- Phase 2: TRACE — Map All Dependencies (Inside AND Outside)
- Phase 3: DIAGNOSE — Find Every Issue
- Phase 4: FIX — Repair Everything Systematically
- Phase 5: VERIFY — Confirm Everything Works
- Red Flags — STOP and Return to Current Phase
- Common Rationalizations
- Anti-Patterns — NEVER do these
- Related Skills
- Quick Reference
What does the focused-fix skill do?
Use when the user asks to fix, debug, or make a specific feature/module/area work end-to-end. Triggers: 'make X work', 'fix the Y feature', 'the Z module is broken', 'focus on [area]'. Not for quick single-bug fixes — this is for systematic deep-dive repair across all files and dependencies.
How do I install it?
Run `npx skills add alirezarezvani/claude-skills --skill focused-fix --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.