Bug capture
Portable AI-engineering skills for Claude Code, Codex, and coding agents: bounded scope, mini-specs, vertical slices, verification, ship gates, and handoff.
npx -y skills add tmusser/ai-engineering-skills --skill bug-captureAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Preserve discovered bugs as BUGS.md entries.
SKILL.md
1.1 KB, as published. Nobody here has run it
Bug Capture
Purpose
Preserve discovered bugs as artifacts.
When to use
Use when a bug is found, whether or not it is fixed in the current session.
Inputs
- Observed behavior
- Expected behavior
- Reproduction steps
- Affected files
- Verification command
Workflow
- Create or update
BUGS.md. - Add a bug title.
- Record observed and expected behavior.
- Write reproduction steps.
- List affected files.
- Add hypothesis and status.
- Record verification command.
- Add resolution if fixed.
Outputs
BUGS.mdentry with bug title, observed behavior, expected behavior, reproduction steps, affected files, hypothesis, status, verification command, and resolution if fixed
Stop conditions
- The bug is captured well enough for another session to reproduce.
- The issue is not a bug and should become a decision or task instead.
Anti-patterns
- Leaving bug knowledge trapped in chat history.
- Recording "broken" without reproduction steps.
- Closing a bug without verification evidence.