issue-workflow

Close a GitHub issue with proper workflow checks (checklist completion, close reason)

Create a GitHub issue following the issue workflow (proper type, structured body, area-prefixed title)

Fetch a GitHub issue, analyze requirements against the codebase, and create an implementation plan with branch

Check repository GitHub configuration against issue workflow requirements and propose fixes

Review open GitHub issues — find stale/zombie/blocked items, categorize by health, and suggest triage actions

Use this agent when you need to analyze the health of open GitHub issues across a repository. This agent performs comprehensive triage: categorizes issues by staleness, identifies zombies, checks blocked items, and produces actionable recommendations. Trigger this agent proactively when the user discusses backlog health, asks about stale issues, mentions cleaning up issues, or wants an overview of open work. <example> Context: User asks about their backlog user: "How does my backlog look? Any issues I should clean up?" assistant: "I'll analyze your open issues to identify anything stale or blocked." <commentary> User wants backlog health assessment — trigger issue-triage agent. </commentary> </example> <example> Context: User mentions stale issues user: "Are there any zombie issues I should close?" assistant: "Let me review all open issues and find any that haven't had activity." <commentary> User specifically asks about zombie/stale issues — trigger issue-triage agent. </commentary> </example> <example> Context: User is planning next work user: "What should I work on next? Let me see what's open." assistant: "I'll analyze your open issues to give you a prioritized overview." <commentary> User wants to pick next work from open issues — trigger issue-triage to categorize and surface the most relevant items. </commentary> </example>

This project uses a custom GitHub Issues workflow with specific conventions that differ from defaults — you must consult this skill rather than giving generic advice. Contains: required issue body template (Problem/Approach/Acceptance Criteria/Tasks/Notes), mandatory branch naming format (issue/{N}-{desc}), label rules (only blocked/stale/pinned allowed), issue sizing with checklists, zombie detection (30-day stale, 44-day auto-close), and triage decision framework. Trigger whenever the conversation touches: creating/structuring issues, branch naming, backlog organization, triage, stale/zombie issues, closing workflow, PR closing keywords, label strategy, issue sizing, blocked issues, or work tracking — even without the word "issue".