How this skill is triggered — by the user, by Claude, or both
Slash command
/code-quality:fix-bugsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Fix the bugs specified by number in `$ARGUMENTS` and update `bugs-summary.md` to reflect the fixes.
Fix the bugs specified by number in $ARGUMENTS and update bugs-summary.md to reflect the fixes.
$ARGUMENTS is a space-separated list of bug numbers from bugs-summary.md. Examples:
/fix-bugs 1 2 3 fixes bugs 1, 2, and 3/fix-bugs 4 fixes bug 4 onlyIf $ARGUMENTS is empty, ask the user which bugs to fix.
Read bugs-summary.md: Read the file from the project root. If it does not exist, tell the user to run
/find-bugs first and stop.
Parse bug numbers: Extract the requested bug numbers from $ARGUMENTS. If any number does not correspond to an
Open bug in the file, warn the user and skip that number. If a requested bug is already marked as FIXED, tell
the user and skip it.
For each bug to fix (in numeric order):
a. Read the relevant source file(s) referenced in the bug description.
b. Read existing test files for the affected code to understand the current test coverage and patterns.
c. Implement the fix: Make the minimum change needed to resolve the bug. Follow project conventions:
d. Add or update tests to verify the fix:
e. Run the test suite using the project's test command to confirm the fix doesn't break anything and the new tests pass. If tests fail, investigate and fix the issue before moving on.
Update bugs-summary.md: Rewrite the file with the following structure:
# Bug Summary
## Fixed
### N. Short title (FIXED)
**File:** `path/to/file.ext`
Original description of the bug.
**Fix:** Description of what was changed and what tests were added.
## Open
### M. Short title
(remaining unfixed bugs)
## Design Observations (not bugs, but worth noting)
(unchanged)
(FIXED) to its titleRun tests one final time to confirm everything is green.
Report: Summarize what was fixed, what tests were added, and confirm all tests pass.
$ARGUMENTS — do not fix other bugs or make unrelated improvements.npx claudepluginhub mattbobambrose/mattbobambrose-claude-skills --plugin code-qualityFixes bugs using test-first loop: add minimal failing reproduction test, apply smallest fix to affected module, verify full test suite and linters. Use for reported bugs needing verified low-impact fixes.
Receives bug reports from QA agents and implements focused, minimal fixes. Works with any tech stack.
Fixes scoped bugs via lightweight TDD workflow: parses description, applies project standards, reproduces with failing test, implements fix, verifies, escalates complex issues.