bug-fix-iteration
Systematic approach to fixing bugs reported via pasted logs. Prevents the agent from making broad changes that introduce regressions when only a targeted fix is needed. [GENERATED BY MOTIF — review and customize]
Best use case
bug-fix-iteration is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Systematic approach to fixing bugs reported via pasted logs. Prevents the agent from making broad changes that introduce regressions when only a targeted fix is needed. [GENERATED BY MOTIF — review and customize]
Teams using bug-fix-iteration 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
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/bug-fix-iteration/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How bug-fix-iteration Compares
| Feature / Agent | bug-fix-iteration | 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?
Systematic approach to fixing bugs reported via pasted logs. Prevents the agent from making broad changes that introduce regressions when only a targeted fix is needed. [GENERATED BY MOTIF — review and customize]
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
# Bug Fix Iteration Systematic approach to fixing bugs reported via pasted logs. Prevents the agent from making broad changes that introduce regressions when only a targeted fix is needed. ## When to Use - User pastes error logs, stack traces, or console output - User says 'it's still broken' or 'that didn't work' - Especially when: previous fix attempt didn't resolve the issue - Don't skip when: the error seems 'obvious' -- still follow the process ## Instructions 1. Read the pasted logs carefully - identify the exact error message and location 2. If error is ambiguous, ask the user one clarifying question before proceeding 3. Check if this is a known issue pattern (same file/component as previous bugs) 4. Propose a targeted fix that addresses only the specific error 5. Do NOT refactor or modify unrelated code in the same change 6. Apply the fix 7. Ask user to test and report back 8. If fix doesn't work after 2 attempts, step back and investigate root cause more broadly ## Best Practices - Read the entire error message, not just the first line - Fix one thing at a time -- don't bundle multiple changes - **Avoid:** Don't refactor code that isn't related to the bug - Always ask the user to verify the fix worked ## Common Pitfalls | Problem | Solution | |---|---| | Agent modifies unrelated code, causing new bugs | Only touch files directly related to the reported error | | Agent proposes sweeping refactor instead of targeted fix | Fix the bug first; propose refactoring separately if needed | | Going in circles with the same fix approach | After 2 failed attempts, investigate root cause from a different angle | ## Key Constraints - Never modify files unrelated to the reported bug - Always ask the user to verify after applying a fix - After 2 failed fix attempts, change your investigation approach