bowen31337/bug-report-agent-skills
bug-report-processor
VerifiedProcesses bug reports from markdown files exported from any ticket system (Linear, GitHub Issues, Bugzilla, etc.), extracts reproduction steps, error logs, and environment details. Manages debugging workflow through Detective Methodology including reproduction, investigation, root cause analysis, fix verification, and regression testing. Use when handling bug reports, debugging issues, or tracking bug resolution.
assets/templates/investigation_template.md
View on GitHub# Investigation Notes: [BUG-ID]
## Bug Summary
- **Title**: [Bug title]
- **Severity**: [critical/high/medium/low]
- **Status**: [current status]
- **Current Phase**: [detective phase]
## Reproduction Results
- **Reproduced**: [Yes/No/Intermittent]
- **Environment Used**: [environment details]
- **Deviation from Steps**: [any deviations]
## Investigation Timeline
### [Date] - Initial Analysis
- Reviewed bug report
- Analyzed stack trace
- Key findings:
- [Finding 1]
- [Finding 2]
### [Date] - Hypothesis Testing
- Tested hypothesis: [description]
- Result: [confirmed/rejected]
- Evidence: [supporting evidence]
## Hypotheses
### HYP-1: [Hypothesis description]
- **Status**: [pending/testing/confirmed/rejected]
- **Evidence**:
- [Evidence point 1]
- [Evidence point 2]
- **Conclusion**: [conclusion if any]
### HYP-2: [Hypothesis description]
- **Status**: [pending/testing/confirmed/rejected]
- **Evidence**:
- [Evidence point 1]
- **Conclusion**: [conclusion if any]
## Root Cause Analysis
### Identified Root Cause
[Detailed description of the root cause]
### Contributing Factors
1. [Factor 1]
2. [Factor 2]
### Responsible Code
- **File**: [file path]
- **Line(s)**: [line numbers]
- **Commit**: [commit hash if known]
## Fix Approach
### Proposed Fix
[Description of the fix approach]
### Files to Modify
1. [file1.py] - [what to change]
2. [file2.py] - [what to change]
### Risks
- [Potential risk 1]
- [Potential risk 2]
## Verification Plan
- [ ] Reproduce bug before fix
- [ ] Apply fix
- [ ] Verify bug no longer occurs
- [ ] Run related unit tests
- [ ] Run regression tests
## Notes
[Additional notes, observations, or context]
---
*Last Updated: [timestamp]*
*Investigator: [name]*
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |