afc:triage

/afc:triage — PR & Issue Triage

Collects open PRs and issues, analyzes them in parallel batch, and produces a priority-ranked triage report. Uses lightweight analysis first (no checkout), then selective deep analysis with worktree isolation for PRs that require build/test verification.

Pre-fetched Context

!gh pr list --json number,title,headRefName,author,labels,additions,deletions,changedFiles,createdAt,updatedAt,reviewDecision,isDraft --limit 50 2>/dev/null || echo "PR_FETCH_FAILED"

!gh issue list --json number,title,labels,author,createdAt,updatedAt,comments --limit 50 2>/dev/null || echo "ISSUE_FETCH_FAILED"

Arguments

• $ARGUMENTS — (optional) Triage scope
  • --pr — PRs only
  • --issue — Issues only
  • --all — Both PRs and issues (default)
  • Specific numbers (e.g., #42 #43) — Analyze only those items
  • --deep — Force deep analysis (worktree) for all PRs

Execution Steps

1. Collect Targets

Use the pre-fetched context above. If fetch failed, fall back to:

"${CLAUDE_SKILL_DIR}/../../scripts/afc-triage.sh" "$ARGUMENTS"

Apply $ARGUMENTS filtering: skip irrelevant items based on --pr, --issue, or specific numbers.

Empty backlog early-exit: If both PR list and issue list are empty (zero open items after filtering), output a clean-backlog summary and exit:

Triage complete — backlog is clean
├─ Open PRs: 0
├─ Open issues: 0
└─ No items require attention

Skip all subsequent phases.

2. Phase 1 — Lightweight Parallel Batch (no checkout)

Spawn all agents in a single message (parallel batch, max 5 concurrent).

PR Analysis

See prompt template: pr-analysis-prompt.md

Task("Triage PR #{number}: {title}", subagent_type: "general-purpose",
  prompt: "<contents of pr-analysis-prompt.md with placeholders filled>")

Issue Analysis (batch of 5 per agent)

Task("Triage Issues #{n1}-#{n5}", subagent_type: "general-purpose",
  prompt: "Analyze these issues:
  {issue list with titles, labels, comment count}

  For each issue:
  1. gh issue view {number} --comments
  2. Classify:
     - Type: Bug|Feature|Enhancement|Question|Maintenance (adapt to project labels)
     - Priority: P0 (blocking/critical) | P1 (high impact) | P2 (normal) | P3 (low/nice-to-have)
     - Effort: Small|Medium|Large
     - Related PRs (if any mentioned)
  3. One-line summary

  Output per issue:
  ISSUE #{number}: {title}
  TYPE: ...
  PRIORITY: P0|P1|P2|P3
  EFFORT: Small|Medium|Large
  RELATED_PR: #N or none
  SUMMARY: ...")