Agent skill
fix
Debugs and fixes issues systematically. Use when something is broken, throwing errors, or behaving unexpectedly.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/fix-djnsty23-claude-auto-dev
SKILL.md
Fix Workflow
On "fix" or "debug"
Step 1: Identify the Problem
question: "What's the issue?"
options:
- { label: "Build error", description: "npm run build fails" }
- { label: "Runtime error", description: "App crashes or throws" }
- { label: "UI bug", description: "Something looks wrong" }
- { label: "I'll describe it", description: "Custom issue" }
Step 2: Gather Context
Build error:
npm run build 2>&1
# Capture and parse error output
Runtime error:
# Check browser console
agent-browser run --task "Go to localhost:3000, open dev console, report any errors"
# Or check server logs
npm run dev 2>&1 | tail -50
UI bug:
# Take screenshot
agent-browser run --task "Go to localhost:3000/[page], screenshot the issue"
# Inspect element
agent-browser run --task "Inspect [element], report CSS and structure"
Step 3: Analyze Root Cause
Common patterns:
| Error Type | Likely Cause |
|---|---|
Cannot find module |
Missing import or package |
Type 'X' is not assignable |
TypeScript mismatch |
undefined is not a function |
Null/undefined access |
Hydration mismatch |
Server/client render diff |
CORS error |
API endpoint config |
401 Unauthorized |
Auth token issue |
Step 4: Fix
- Make the minimal change needed
- Don't refactor unrelated code
- Don't add "improvements"
- Test the fix immediately
Step 5: Verify
npm run build
# If passes, test the specific feature
If build or feature test fails, return to Step 4 with updated error info. Maximum 3 fix attempts — if still failing after 3 tries, report the remaining issue and stop.
Step 6: Document
Append to progress.txt:
"## [DATE]: Fixed [issue]
- Root cause: [explanation]
- Solution: [what was changed]
- Files: [list of modified files]"
Quick Fix Commands
| Say | Action |
|---|---|
fix build |
Run build, auto-fix errors |
fix types |
Fix TypeScript errors only |
fix [file] |
Focus on specific file |
Common Auto-Fixes
Missing import:
// Add at top of file
import { Thing } from './path'
Null safety:
// Before
obj.property
// After
obj?.property
Type assertion:
// When type is known but TS doesn't infer
(value as ExpectedType)
When to Stop
STOP and ask user if:
- Fix requires architectural change
- Multiple valid approaches exist
- Fix might break other features
- Root cause is unclear after 3 attempts
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?