Skip to content
Back to skills

Better Bug Fix

ASecurity

Bug-fixing workflow that starts by writing a failing test to reproduce the bug, then uses subagents to propose fixes and verifies with passing tests. Use when a user reports a bug, asks to fix a bug, or wants a regression test first.

  • 666 stars
  • 0 votes
  • 0 copies
  • 10 views
  • Added February 8, 2026
developmentrailsdebuggingapi

Works with

  • api

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add majiayu000/claude-skill-registry --skill better-bug-fix --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Better Bug Fix?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Better Bug Fix
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-better-bug-fix/badge)](https://www.skillsdirectory.com/skills/majiayu000-better-bug-fix)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: better-bug-fix
description: Bug-fixing workflow that starts by writing a failing test to reproduce the bug, then uses subagents to propose fixes and verifies with passing tests. Use when a user reports a bug, asks to fix a bug, or wants a regression test first.
---

# Better Bug Fix

Follow a test-first debugging workflow that proves the bug and validates the fix.

## Workflow

1. Triage and scope the bug.
   - Restate the symptom and expected behavior in one sentence.
   - Identify the affected area (files, module, API, UI).

2. Write a minimal failing test first.
   - Add the smallest test that reproduces the bug.
   - Prefer existing test frameworks and patterns in the repo.
   - If no tests exist, create a minimal repro harness as close as possible to existing structure.

3. Run tests to confirm failure.
   - Execute the narrowest test command that includes the new test.
   - Record the failing output or error signature.

4. Delegate fixes to subagents.
   - Spawn 2-3 subagents with clear ownership of investigation/fix ideas.
   - Ask each to propose a fix and the rationale, referencing the failing test.
   - Keep their scopes non-overlapping (e.g., data flow, edge cases, API contract).

5. Implement the best fix.
   - Apply the most plausible fix based on test and codebase conventions.
   - Keep the change minimal and focused on the bug.

6. Prove the fix.
   - Re-run the failing test(s) and any relevant nearby tests.
   - Ensure the new test passes and no regressions are introduced.

7. Report clearly.
   - Explain the root cause, the test added, and why the fix works.
   - Call out any remaining risks or follow-ups.

## Guardrails

- Do not attempt a fix before a reproducing test exists.
- If a test cannot be written, explicitly explain why and propose the closest alternative (repro script or manual steps).
- Avoid refactors unless necessary to make the test feasible.
- Keep changes small; prefer surgical fixes.

## Subagent Prompt Template

Use this template when spawning subagents:

"""

You are a subagent investigating a bug. The reproducing test is failing. Please:

1. Identify the likely root cause in the code.
2. Propose a minimal fix.
3. Note any tradeoffs or additional tests to add.

**Stay within your assigned scope.**

"""

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.