bug_report.md•2.57 kB
---
name: Bug Report
about: Report a bug or issue
title: 'bug: '
labels: ['bug']
assignees: ''
---
## Description
<!-- Provide a clear and concise description of the bug -->
## Steps to Reproduce
1.
2.
3.
## Expected Behavior
<!-- What did you expect to happen? -->
## Actual Behavior
<!-- What actually happened? -->
## Environment
- Module: <!-- e.g., Core, API, Documentation, Testing, Build -->
- File(s): <!-- affected file paths -->
## Required Labels
<!-- You MUST include all of these label categories -->
### Priority Level
<!-- Select ONE by replacing [ ] with [x] -->
- [ ] `P0` - Critical (service down, security issue)
- [ ] `P1` - High (blocking functionality)
- [ ] `P2` - Medium (important but not blocking)
- [ ] `P3` - Low (minor improvements)
- [ ] `P4` - Trivial (cosmetic, nice-to-have)
### Status Label
<!-- Select ONE by replacing [ ] with [x] -->
- [ ] `status:ready` - Ready for implementation
- [ ] `status:in-progress` - Currently being worked on
- [ ] `status:blocked` - Cannot proceed due to dependencies
- [ ] `status:needs-info` - Requires additional information
- [ ] `status:review` - Ready for or in review
- [ ] `status:untriaged` - Not yet assessed
### Area Labels
<!-- Select ALL that apply by replacing [ ] with [x] -->
**Module:**
- [ ] `area:core` - Core module
- [ ] `area:api` - API functionality
- [ ] `area:build` - Build system
- [ ] `area:dist` - Distribution
**Content:**
- [ ] `area:documentation` - Documentation
- [ ] `area:testing` - Testing
- [ ] `area:performance` - Performance
- [ ] `area:refactor` - Refactoring
## Additional Context
<!-- Add any other context about the bug here -->
## Advanced Troubleshooting (for complex bugs)
<!-- For stubborn bugs, consider using these advanced techniques -->
### Sequential Analysis
<!-- Break down the problem investigation into clear steps -->
### External Research
<!-- Include any external documentation or references consulted -->
### Previous Similar Issues
<!-- Link to any similar issues that have been solved before -->
## Related Issues
<!-- Link any related issues -->
## Reminder: GitHub Issue Management Requirements
<!-- Do not remove this section -->
### Before Closing:
1. Check off all criteria
2. Add implementation comment with:
- Implementation Details
- Key Implementation Elements (3+ points)
- Lessons Learned (3+ insights)
- Challenges/Solutions
- Future Considerations
3. Add verification statement:
"✅ VERIFICATION: I have completed all GitHub documentation requirements including: [list all requirements]"