issue-creationlisted

## When to Use Use this skill when: - Creating a GitHub issue (bug report or feature request) - Helping a contributor file an issue - Triaging or approving issues as a maintainer --- ## Critical Rules 1. **Blank issues are disabled** — MUST use a template (bug report or feature request) 2. **Every issue gets `status:needs-review` automatically** on creation 3. **A maintainer MUST add `status:approved`** before any PR can be opened 4. **Questions go to repository discussions**, not issues --- ## Workflow ``` 1. Search existing issues for duplicates 2. Choose the correct template (Bug Report or Feature Request) 3. Fill in ALL required fields 4. Check pre-flight checkboxes 5. Submit → issue gets status:needs-review automatically 6. Wait for maintainer to add status:approved 7. Only then open a PR linking this issue ``` --- ## Issue Templates ### Bug Report Template: `.github/ISSUE_TEMPLATE/bug_report.yml` Auto-labels: `bug`, `status:needs-review` #### Required Fields | Field | Description | |-------|-------------| | **Pre-flight Checks** | Checkboxes: no duplicate + understands approval workflow | | **Bug Description** | Clear description of the bug | | **Steps to Reproduce** | Numbered steps to reproduce | | **Expected Behavior** | What should have happened | | **Actual Behavior** | What happened instead (include errors/logs) | | **Operating System** | Dropdown: macOS, Linux variants, Windows, WSL | | **Agent / Client** | Dropdown: Claude Code, Pi, Gemini CLI, Curs