About fix-bug
fix-bug is a structured skill for diagnosing and fixing reported software bugs. It guides developers from reproducing the issue with focused tests through a minimal implementation change and verification.
Key features
- 01Clarify expected and actual behavior
- 02Collect lightweight debugging evidence
- 03Create a focused regression test
- 04Make a small cohesive fix
- 05Run checks and summarize the cause
Use cases
- 01Reproduce a reported bug reliably
- 02Add a regression test before changing code
- 03Verify a fix and prepare repository changes
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/fix-bugin Claude Code to confirm it loaded.
Details
From the project READMEBug fix workflow
- Understand the reported bug precisely.
- Identify the expected behavior, the actual behavior, and the smallest scope that reproduces the problem.
- Inspect the existing tests and locate the best place to extend them.
- Prefer enhancing an existing focused test file over adding a broad new one.
- Before modifying tests, gather debugging evidence that helps explain the failure mode.
- Use logging, screenshots, traces, or other lightweight diagnostics that fit the stack.
- Enhance the tests until they reproduce the bug.
- If a relevant test already fails for the bug, keep it as the reproduction and tighten it only if needed.
- Stop once the reproduction is minimal, reliable, and clearly tied to the reported bug.
- Fix the implementation without weakening the new or existing assertions.
- Keep the code change as small and cohesive as possible.
- Run the enhanced tests and confirm they pass with the fix in place.
- If the repository workflow requires broader verification, run the relevant checks after the targeted tests pass.
- Summarize the root cause, the test enhancement, and the implementation fix.
- Commit and push the changes, then run either the
open-prorupdate-prskill.
Comments
Markdown supported