Best use case
fix is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Diagnose and fix bugs with surgical precision.
Teams using fix should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/fix/SKILL.md --create-dirs "https://raw.githubusercontent.com/lionbenjamin/agent-templates/main/skills/fix/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/fix/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How fix Compares
| Feature / Agent | fix | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Diagnose and fix bugs with surgical precision.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Fix Skill Root cause analysis and surgical bug fixes. ## When to Activate This skill is relevant when: - Bug reports need investigation - Errors need diagnosis and fixing - Stack traces need analysis - Regression tests needed - Production issues require fixes - Root cause analysis required ## Core Principles ### Root Cause Obsessed - Don't just patch the symptom - Find the underlying disease - Understand why it broke - Fix the actual problem - Prevent future occurrences ### Log Whisperer - Read stack traces carefully - See patterns in error logs - Trace execution paths - Use logging strategically - Follow the error chain ### Test-Driven Fixes - Bug isn't fixed until test proves it - Write failing test first - Fix makes test pass - Regression test prevents recurrence - Green tests confirm fix ### Defensive Coding - Assume everything will fail - Assert early, assert often - Validate inputs thoroughly - Handle edge cases - Add safety checks ## Quick Checks For bug fixes, verify: - [ ] Bug reproduction case created - [ ] Failing test demonstrates bug - [ ] Stack trace or error message analyzed - [ ] Execution path traced - [ ] Root cause identified - [ ] Hypothesis formulated - [ ] Hypothesis validated against code - [ ] Fix planned and documented - [ ] Code changes applied - [ ] Reproduction test now passes - [ ] Related tests still pass - [ ] No side effects introduced - [ ] Regression test added - [ ] Safety checks added if needed - [ ] Fix is clean, no technical debt ## Diagnostic Process ### Reproduce - Get stack trace or error message - Create failing test case - Document exact reproduction steps - Verify the failure (red state) ### Diagnose - Trace execution path - Formulate hypothesis - Validate hypothesis - Identify root cause ### Fix Strategy - Document root cause - Plan the fix - Define verification method - Consider side effects ### Verify & Protect - Test passes (green state) - Run regression checks - Add assertions - Add type checks - Prevent recurrence ## Fix Documentation ### Root Cause What exactly went wrong and why ### The Fix What code changes were made ### Prevention How we stopped it from recurring ### Verification How we proved it's fixed
Related Skills
We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.