fix-bug

Automate end-to-end bug fixing with test-driven development and regression tests.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/sQVe/cape --skill fix-bug-sqve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-bug
Source: https://github.com/sQVe/cape/tree/main/skills/fix-bug
Command: npx skills add https://github.com/sQVe/cape --skill fix-bug-sqve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end bug fixes require coordinating discovery, reproduction, testing, and closure, which can be lengthy and error-prone without a structured workflow. This Skill automates that end-to-end flow and enforces evidence-based closure.

Core Features & Use Cases

  • Adopt or create the br bug, reproduce, fix via the TDD cycle, verify, and close.
  • Dispatches cape:debug-issue when no br bug exists to investigate and generate a root cause with evidence and reproduction steps.
  • Evidence-based closure: append an outcome to the br bug, verify regression tests, and present a fix summary for approval.

Quick Start

Describe the bug clearly to initiate the end-to-end fix cycle.

Frequently Asked Questions about fix-bug

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

FAQPage Schema
How do I automate end-to-end bug fixes with regression testing?

Automate end-to-end bug fixes by adopting a bug report, reproducing the issue, applying a test-driven development workflow, verifying the regression test, and closing the bug with evidence.

What is evidence-led bug closure in an automated workflow?

Evidence-led bug closure appends a verified outcome to the bug report, confirms regression tests pass, and presents a fix summary for approval to ensure the resolution is fully validated.

How do I fix a reported bug when no bug report exists?

When no bug report exists, the workflow dispatches a debug-issue investigation to generate a root cause with evidence and reproduction steps before proceeding with the test-driven fix.

Can I use test-driven development for resolving diagnosed bugs?

Yes, test-driven development is used for resolving diagnosed bugs by writing a failing regression test, applying the fix, and verifying the test passes to ensure evidence-based closure.

What's the best way to ensure regression tests are added to every bug fix?

To ensure regression tests are added to every bug fix, use an automated workflow that enforces a test-driven development cycle and verifies the regression test before closing the bug report.