Antfu Issue Triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate...
Install
npx skills add antfu/skills --skill antfu-issue-triage -g -a claude-code -y- Repository
- antfu/skills6k
- Category
- Git and review
- Updated
- 5d ago
- License
- MIT
- Context cost
- Mediumabout 2,886 tokens
- Runs scripts
- No, instructions only
What it does
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues and PRs.
Issue Triage
Go through the open issues and PRs of the current repo (gh repo view --json nameWithOwner) and propose clean-up actions. Maintainers decide; the agent investigates.
Hard Rules
- Read-only until confirmed. Never comment, label, close, or edit before the user approves the action tables. Reads (
gh issue view,gh apiGET,gh search) are fine. - Every comment says it is automated by an agent. End with a separate last line (blank line before it):
🤖 *Automated by an agent.* - Comments are short and plain. Write them in simple English (use the
simple-englishskill if available): 1-3 short sentences, active voice, no jargon, no filler. Write each comment fresh for the item. Do not reuse a fixed template. Always include the link (PR, commit, release, or canonical issue) that justifies the action. - Only apply approved rows. If the user edits or drops rows, follow their edits exactly.
- Be conservative: when unsure, propose
keep open(with labels if useful) instead of closing. Do not close items with active maintainer discussion, an open linked PR, or a milestone unless the user asks. - Use plain hyphens; no em or en dashes.
