What problem does it solve?
Poorly formatted, untagged, or duplicate GitHub issues lead to a messy backlog, wasted effort, and difficulty in prioritizing and tracking work, hindering project progress.
Core Features & Use Cases
- Label Verification & Selection: Mandates checking existing labels (
gh label list) and selecting appropriate types (bug, enhancement, chore) before creation, ensuring proper categorization.
- Standardized Format: Enforces a clear title pattern (
[Component] Description) and a structured body (Context, Expected, Current, Reproduction) for actionable and easily searchable issues.
- Systemic Detection & Avoidance: Guides when to create an issue (systemic, cross-app, technical debt) versus when to skip (immediate fix, trivial, already tracked), preventing backlog noise.
- Use Case: When discovering a systemic bug that cannot be fixed immediately, use this skill to create a well-formatted GitHub issue with verified labels, clear reproduction steps, and proper context, ensuring it's actionable and trackable.
Quick Start
Verify existing GitHub labels using gh label list before creating a new issue.