pr-triage

PR Triage

Workflow in 3 phases: automatic audit → opt-in deep review → comments with mandatory user validation.

When to Use

Skill	Usage	Output
/pr-triage	Triage, review, and comment on PRs	Action table + reviews + posted comments
/repo-recap	General recap to share with the team	Markdown summary (PRs + issues + releases)

Triggers:

• Manually: /pr-triage or /pr-triage all or /pr-triage 42 57
• Proactively: when >5 open PRs without review, or PR stale >14d detected

---

Language

• Check the argument passed to this skill
• If fr or french → output tables and summary in French
• If en, english, or no argument → English (default)
• Note: GitHub comments (Phase 3) are ALWAYS in English (international audience)

---

Preconditions

git rev-parse --is-inside-work-tree
gh auth status

If either fails, stop and explain what's missing.

---

Phase 1 — Audit (always executed)

Data Gathering (parallel commands)

# Repo identity
gh repo view --json nameWithOwner -q .nameWithOwner

# Open PRs with full metadata
gh pr list --state open --limit 50 \
  --json number,title,author,createdAt,updatedAt,additions,deletions,changedFiles,isDraft,mergeable,reviewDecision,statusCheckRollup,body

# Collaborators (to distinguish "our PRs" from external ones)
gh api "repos/{owner}/{repo}/collaborators" --jq '.[].login'

Collaborators fallback — if gh api .../collaborators fails (403/404):

gh pr list --state merged --limit 10 --json author --jq '.[].author.login' | sort -u

If still ambiguous, ask the user via AskUserQuestion.

For each PR, fetch existing reviews AND modified files:

gh api "repos/{owner}/{repo}/pulls/{num}/reviews" \
  --jq '[.[] | .user.login + ":" + .state] | join(", ")'

gh pr view {num} --json files --jq '[.files[].path] | join(",")'