Triage

Project: !basename $(git rev-parse --show-toplevel 2>/dev/null) 2>/dev/null || basename $PWD

Branch: !git branch --show-current 2>/dev/null || echo "unknown"

Open issues: !gh issue list --state open --json number,title --jq '.[] | "#\(.number) \(.title)"' 2>/dev/null || echo "none"

Last tag: !git describe --tags --abbrev=0 2>/dev/null || echo "none"

Recent commits: !git log --oneline -5 2>/dev/null || echo "none"

Validates every open GitHub issue, closes those that are invalid, surfaces complex ones

for planning discussion, then fixes and promotes all remaining actionable issues.

Step 0: Pre-flight check

gh auth status 2>&1 || { echo "ERROR: gh is not authenticated. Run: gh auth login"; exit 1; }

Step 1: Fetch all open issues

gh issue list --state open --limit 100 --json number,title,body,labels,createdAt \
  --jq '.[] | {number, title, labels: [.labels[].name], createdAt, body}'

Read the full body of any issues where context is needed:

gh issue view <number> --json number,title,body,labels,comments

Also read the project files to understand current state before assessing anything:

• README.md — stated purpose and feature set
• CLAUDE.md — current status, known decisions, next steps

Step 2: Classify each issue

For every open issue, classify it as one of:

• Invalid — already fixed, a duplicate, not reproducible, out of scope, or based on a

misunderstanding. Evidence must be clear.

• Complex — valid but requires significant design decisions, breaking changes, or

multi-step implementation that warrants planning discussion before proceeding.

• Actionable — valid, well-scoped, and fixable now without further input.

Build a classification table before taking any action:

Step 3: Close invalid issues

For each invalid issue, post a closing comment that explains why it is being closed, then close it:

gh issue comment <number> --body "$(cat <<'EOF'
Closing as invalid: <specific reason — already fixed in <commit/PR>, duplicate of #N,
not reproducible because <evidence>, or out of scope because <reason>>.

<If already fixed: reference the commit or PR that resolved it.>
<If duplicate: reference the canonical issue.>
EOF
)"

gh issue close <number> --reason "not planned"

Use --reason "completed" if the issue was already resolved in code.

Step 4: Surface complex issues for planning

Stop and present complex issues to the user before proceeding. Format clearly:

Complex issues — planning needed before proceeding:

For each complex issue:

• #N: