fix-bug
Skill0 starsChanged 5 months agoMITView on GitHub
Fix bugs from docs/bugs.md. Lists unfixed bugs in priority order for selection, or accepts a bug number directly. Investigates, implements, tests, and updates the bug status.
44 other projects use a version of this.
Adopted by
Most recently taken up by
- seancabalse/agentic-playbooktheir own version, first seen Nov 16, 2026
- Slama-Consulting/proofbenchtheir own version, first seen Nov 15, 2026
- todoist/todoist-clitheir own version, first seen Nov 15, 2026
- Doist/todoist-aitheir own version, first seen Nov 9, 2026
- Doist/todoist-clitheir own version, first seen Nov 8, 2026
- danielvm-git/bigpowerstheir own version, first seen Nov 6, 2026
Used with
Projects with it also use improvement, build-feature and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
kiminmonacoSkillimprovement
Guide for making improvements to existing ClaudeBar functionality using TDD. Use this skill when: (1) Enhancing existing features (not adding new ones) (2) Improving UX, performance, or code quality (3) User asks "improve X", "make Y better", or "enhance Z" (4) Small enhancements that don't require full architecture design For NEW features, use implement-feature skill instead.
Also in 4 projects that use this
sirakinbSkillbuild-feature
Autonomous task loop that picks ready tasks, implements them, updates progress.txt, commits, and repeats. Use when asked to 'build feature', 'run the loop', or 'implement these tasks'.
Also in 5 projects that use this
kiminmonacoSkillimplement-feature
Guide for implementing features in ClaudeBar following architecture-first design, TDD, rich domain models, and Swift 6.2 patterns. Use this skill when: (1) Adding new functionality to the app (2) Creating domain models that follow user's mental model (3) Building SwiftUI views that consume domain models directly (4) User asks "how do I implement X" or "add feature Y" (5) Implementing any feature that spans Domain, Infrastructure, and App layers
Also in 7 projects that use this
SentrySkillwrite-tests
Write tests following project conventions. Use when adding new tests or modifying existing ones.
Also in 6 projects that use this
JetBrainsSkillcreate-plan
Research the codebase and create an implementation plan with architecture notes, design document, and track decomposition. Use when starting a new feature or large change.
Also in 4 projects that use this
JasonPaffSkillimplement-plan
Execute implementation plan with structured tracking and validation using subagent architecture
Also in 3 projects that use this
Other versions44 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 44
- remix-run/react-router★ 57ksame name
- ktorio/ktor★ 15ksame name
- JetBrains/Exposed★ 9.3ksame name
- bytebase/dbhub★ 3.9ksame name
- The-OpenROAD-Project/OpenROAD★ 3.3ksame name
- JamieMason/syncpack★ 2.1ksame name
- tddworks/ClaudeBar★ 1.6ksame name
- Harry-kp/vortix★ 757same name
- Doist/todoist-ai★ 563same name
- tddworks/asc-cli★ 393same name
34 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- add-bugSkill
- add-featureSkill
- list-bugsSkill
- review-my-codeSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
23 rules. 0 are common, 19 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 44 edited versions we read keep these.
19
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 38
Read the bug description, steps to reproduce, and expected vs actual behaviour
- Distinctive: line 40
Search for the root cause using Grep, Read, and Glob
- Distinctive: line 50
Follow all coding conventions from CLAUDE.md
- Distinctive: line 51
Don't introduce unnecessary changes or refactors beyond the bug fix
- Distinctive: line 52
If the fix spans multiple areas, handle each area
- Distinctive: line 53
Add comments only if the fix is non-obvious
- Distinctive: line 58
Add one mapping per area in your project
- Distinctive: line 59
If the bug involves UI behaviour, validate it visually (e.g.
- Distinctive: line 60
If tests fail, diagnose and fix before proceeding
- Distinctive: line 64
Add a Fix details section below the existing fields:
- Distinctive: line 80
If the user selects multiple bugs or says "all":
- Distinctive: line 82
Update each bug's status as you go
- Distinctive: line 83
If one fix is blocked or too complex, skip it, note why, and move to the next
- Very specific: line 88
If docs/bugs.md has no open bugs, say "No open bugs to fix.
- Very specific: line 89
If the requested bug number doesn't exist, say "BUG-{NNN} not found in docs/bugs.md"
- Distinctive: line 90
If the bug is already Fixed, say "BUG-{NNN} is already marked as Fixed"
- Very specific: line 91
If the bug is Won't Fix, say "BUG-{NNN} is marked as Won't Fix — reopen it first with /add-bug or edit docs/bugs.md"
- Distinctive: line 92
If you cannot determine the root cause after investigation, update the status to Confirmed (if it was Reported), describe your findings, …
- Distinctive: line 93
If the fix requires changes to infrastructure, environment variables, or third-party services (e.g.
- Very specific: line 107
Use the <TIMEZONE> timezone for timestamps
- Distinctive: line 108
Always read the relevant code before attempting a fix — never guess
- Distinctive: line 109
Prefer the smallest correct fix over a large refactor
- Distinctive: line 110
If the fix is risky or touches payment/auth code, flag it to the user before applying
“Common” is measured: kept by at least 6 in 10 of the 44 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Fix Bug
Investigate and fix bugs tracked in docs/bugs.md.
Process
- Read
docs/bugs.md— Parse all bug entries. Determine which bug to fix:
- If the user provided a bug number (e.g.
/fix-bug 1,/fix-bug BUG-003): Find that specific bug. If it's already Fixed or Won't Fix, inform the user and stop. - If no bug number provided: Collect all open bugs (statuses: Reported, Confirmed, In Progress) and present them in priority order. Use AskUserQuestion to let the user pick which bug(s) to fix.
- If the user provided a bug number (e.g.
Priority ordering — When listing bugs for selection, sort by:
- Severity: Critical > High > Medium > Low
- Status: In Progress > Confirmed > Reported (prefer bugs already being worked on)
- Age: Older bugs first (earlier reported date)
Display as a numbered list:
Open bugs (prioritised): 1. [BUG-005] 🔴 Critical — Checkout fails when the payment webhook times out (<area-1>) 2. [BUG-002] 🟡 High — File upload stalls on slow connections (<area-2>) 3. [BUG-001] 🔴 Medium — Form changes don't enable the submit button (<area-1>) Enter bug number(s) to fix (e.g. "1" or "1,3"), or "all" to fix everything:- Investigate the bug — Before writing any code:
- Read the bug description, steps to reproduce, and expected vs actual behaviour
- Identify the area (one of your configured project areas — see Configuration) and navigate to the relevant code
- Search for the root cause using Grep, Read, and Glob
- Understand the surrounding code and any related functionality
- Identify the minimal set of files that need to change
- Update status to In Progress — Edit
docs/bugs.mdto change the bug's status:| **Status** | 🔵 In Progress | - Implement the fix — Write the minimal, correct fix:
- Follow all coding conventions from CLAUDE.md
- Don't introduce unnecessary changes or refactors beyond the bug fix
- If the fix spans multiple areas, handle each area
- Add comments only if the fix is non-obvious
- Verify the fix — Run the test suite for the affected area to confirm. Map each area to its test command (configure these for your project):
- For
<area-1>:<test command, e.g. cd frontend && npm test> - For
<area-2>:<test command, e.g. pytest backend/> - Add one mapping per area in your project
- If the bug involves UI behaviour, validate it visually (e.g. with a headed browser / Playwright)
- If tests fail, diagnose and fix before proceeding
- For
- Update status to Fixed — Edit
docs/bugs.mdto update the bug entry:- Change status to
🟢 Fixed - Add a Fix details section below the existing fields:
**Fix details:** - **Fixed:** {YYYY-MM-DD <TIMEZONE>} - **Root cause:** {Brief explanation of what caused the bug} - **Files changed:** {List of files modified} - Change status to
- Report to the user — Summarise:
- What the root cause was
- What was changed and where
- Whether tests pass
- Any follow-up items (e.g. "this should also be tested manually on a real device")
Fixing multiple bugs
If the user selects multiple bugs or says "all":
- Fix them one at a time in priority order
- Update each bug's status as you go
- If one fix is blocked or too complex, skip it, note why, and move to the next
- Provide a summary at the end listing which bugs were fixed and which were skipped
Edge cases
- If
docs/bugs.mdhas no open bugs, say "No open bugs to fix. Nice work!" - If the requested bug number doesn't exist, say "BUG-{NNN} not found in docs/bugs.md"
- If the bug is already Fixed, say "BUG-{NNN} is already marked as Fixed"
- If the bug is Won't Fix, say "BUG-{NNN} is marked as Won't Fix — reopen it first with
/add-bugor edit docs/bugs.md" - If you cannot determine the root cause after investigation, update the status to Confirmed (if it was Reported), describe your findings, and ask the user for guidance rather than guessing at a fix
- If the fix requires changes to infrastructure, environment variables, or third-party services (e.g. payment, storage, or email providers) that can't be done in code, document what needs to be done manually and mark the bug as 🟡 Confirmed with a note
Configuration
Replace these placeholders with your project's values before using the skill:
<area-1>/<area-2>/ … — the modules / sub-projects in your repo (e.g.frontend,backend,api,mobile). Keep this list identical to the areas defined inadd-bug.<test command …>— how to run tests for each area (step 7), e.g.cd frontend && npm test,pytest backend/,flutter test. Add one mapping per area.<TIMEZONE>— the timezone for the Fixed timestamp (e.g.UTC,America/New_York,Europe/London).
See the repository README for the full placeholder reference shared across skills.
Notes
- Use the
<TIMEZONE>timezone for timestamps - Always read the relevant code before attempting a fix — never guess
- Prefer the smallest correct fix over a large refactor
- If the fix is risky or touches payment/auth code, flag it to the user before applying
- Each bug fix should be a separate commit
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

