Agent skill · software engineering · alirezarezvani
focused-fix
Use when a whole feature or module is broken and needs fixing end to end ('make X work', 'the Y module is broken'). Maps every file and dependency of the area before changing anything. Single quick bug fixes do not need it.
Why this skill is useful
Provides a systematic approach to deep-dive debugging and feature repair that includes specific phases and dependency mapping not commonly found in generic documentation.
What it needs
About 9k tokens when loaded. Last updated 2026-08-05. 23,939 stars on the source repository.
What this skill does
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. The Iron Law If you haven't finished Phase 3, you cannot propose fixes. Period. Violating the letter of these phases is violating the spirit of focused repair. Protocol — STRICTLY follow these 5 phases IN ORDER Phase 1: SCOPE — Map the Feature Boundary Before touching any code, understand the full scope of the feature. 1. Ask the user: "Which feature/folder should I focus on?" if not already clear 2. Identify the PRIMARY folder/files for this feature 3. Map EVERY file in that folder — read each one, understand its purpose 4. Create a feature manifest: Phase 2: TRACE — Map All Dependencies (Inside AND Outside) Trace every connection this feature has to the rest of the codebase. INBOUND (what this feature imports): 1. For every import statement in every file in the feature folder: Trace it to its source Verify the source file exists Verify the imported entity (function, type, component) exists and is exported Check if the types/signatures match what the feature expects 2. Check for: Environment variables used (grep for process.env, import.meta.env, os.environ, etc.) Config files referenced Database models/schemas used API endpoints called Third-party packages imported OUTBOUND (what imports this feature): 1. Search the entire codebase for imports from this feature folder 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills alirezarezvani/focused-fix--4727f4