bug-investigation
Investigate a bug/defect. Triggered by 'fix/investigate a bug/defect'
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 21
- Forks
- 1
01 前言 Front Matter
- name
- bug-investigation
- description
- Investigate a bug/defect. Triggered by 'fix/investigate a bug/defect'
03 SKILL.md 正文
If a bug is non-trivial, use /diagnosing-bugs to investigate it.
Generate a root cause analysis of the defect.
A fix can be implemented immediately without an issue/ticket if it has a simple straightforward root cause and fix.
Otherwise, integrate the fix into the current workflow. If you are in the midst of implementation and the implementation changes caused the bug, fix it as part of the implementation.
Issues/Tickets
If there is already a defect ticket, save the root cause analysis on the ticket for the defect. If there is no ticket referenced for a fresh bug report, ask the user if you should create one using /to-tickets. If you know how to search the issue tracker, first search it for a similar bug report. As a bonus suggest how to fix the defect based on your existing defect analysis if you are able, but don't explore the code base further to do that- focus on completing and reporting the root cause analysis.
04 同仓库更多 Skills
easy-issues
Find and work through easy issue-tracker tasks autonomously, simplest first, using one fresh subagent per issue in sequence. Use for clearing straightforward bugs, documentation fixes, and tiny features without operator help.
wrap-up
After implementing, commit and finish your work
verify
Verify software by intentional testing.
update-working-copy
Fetch the latest from the remote. Update the working branch or switch to main if the branch is defunct.
tickets
Break a plan, spec, or conversation into tracer-bullet issues for this repo, creating a parent tracking issue with sub-issues when publishing multiple tickets.
spec
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.