issue-triage

Issue Triage

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

When to Use

Skill	Usage	Output
/issue-triage	Triage, analyze, and comment on issues	Action tables + deep analysis + posted comments
/repo-recap	General recap to share with the team	Markdown summary (PRs + issues + releases)

Triggers:

• Manually: /issue-triage or /issue-triage all or /issue-triage 42 57
• Proactively: when >10 open issues without triage, or issue stale >30d 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 issues with full metadata
gh issue list --state open --limit 100 \
  --json number,title,author,createdAt,updatedAt,labels,assignees,body,comments

# Open PRs (for cross-reference)
gh pr list --state open --limit 50 --json number,title,body

# Recently closed issues (for duplicate detection)
gh issue list --state closed --limit 20 \
  --json number,title,labels,closedAt

# Collaborators (to protect maintainer issues)
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.