gh-issue-filing
Write and triage GitHub issues that AI sub-agents can implement without asking a single follow-up question — the six-section groomed-issue format (verified file:line evidence, literal acceptance criteria, traceability hint), the filing-time label taxonomy, duplicate and cross-reference etiquette between concurrent operators, follow-up filing instead of scope creep, and the recon protocol that classifies stub issues into ready-to-dispatch / needs-spec-input / blocked via a sandboxed cheap-model decision tree with a machine-parseable output contract. Use whenever you are about to file, draft, groom, split, enrich, or triage a GitHub issue or a batch of them — when an operator reports a bug or pastes an error, when a feature request needs to become trackable work, when you discover adjacent work mid-task that must become a follow-up issue rather than scope creep, or when an issue queue needs triage before dispatch — even if the user just says "file this", "make a ticket", or "write that up".
Pinned to revision 6b9d66f636cc, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/gh-issue-filing/SKILL.md
- skills/gh-issue-filing/evals/triggering.json
- skills/gh-issue-filing/references/recon-brief.md
Every link opens the file at its source, pinned to the revision this page describes.