fix-bugs

Fix numbered bugs from bugs-summary.md and add verifying tests.

1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/mattbobambrose/mattbobambrose-claude-skills --skill fix-bugs-mattbobambrose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-bugs
Source: https://github.com/mattbobambrose/mattbobambrose-claude-skills/tree/main/plugins/code-quality/skills/fix-bugs
Command: npx skills add https://github.com/mattbobambrose/mattbobambrose-claude-skills --skill fix-bugs-mattbobambrose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the focused, manual work of taking numbered bug reports from a bugs-summary file, making the minimal code changes to resolve those bugs, and adding tests to prevent regressions so maintainers do not need to perform error-prone, ad hoc fixes.

Core Features & Use Cases

  • Read and parse the project's bugs-summary file to identify open, numbered bugs requested by the user.
  • Inspect relevant source and test files, implement minimal fixes that follow project conventions, and add or update tests that would have failed before the change.
  • Run the project's test suite to verify new and existing tests pass, update the bugs-summary file to mark fixes and describe what changed, and produce a concise report of fixes and test outcomes.
  • Use case: a developer asks to fix specific bug numbers from the bug list, ensuring changes are minimal, tested, and tracked in the summary.

Quick Start

Run the fix-bugs skill with the bug numbers you want fixed, for example: /fix-bugs 1 2

Frequently Asked Questions about fix-bugs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate bug fixes from a bugs-summary file and add verification tests?

To automate bug fixes, this Skill reads numbered bug reports from a bugs-summary file, applies minimal code changes to resolve them, and adds unit tests to prevent regressions. It then runs the project test suite to validate the fixes.

Can I fix specific bug numbers without modifying unrelated source code?

Yes, you can target specific bug numbers by passing them to the Skill. It performs targeted, minimal code changes across only the relevant source and test files, preserving bug numbering and leaving unrelated code untouched.

What is the best way to ensure bug fixes do not cause regressions in my repository?

The best way to prevent regressions is adding targeted verification tests. This Skill writes tests that would have failed before the fix, runs the project's test command to confirm they pass, and updates the bugs-summary with FIXED entries.

Does this bug fixing tool require a specific bug tracking format to work?

Yes, it requires repositories to maintain a numbered bugs-summary.md file. The Skill parses this file to identify open bugs, implements fixes, and updates the summary with descriptions of what changed for each resolved issue.

How do I update a bugs-summary file after applying code fixes?

Updating a bugs-summary file happens automatically after fixing bugs. The Skill marks resolved items with FIXED entries, adds a description of each code change, and produces a concise report of fixes and test outcomes.