# Antfu Issue Triage

Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate...

- Repository: https://github.com/antfu/skills (6032 stars)
- Category: Git and review
- License: MIT
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add antfu/skills --skill antfu-issue-triage -g -a claude-code -y`
Codex: `npx skills add antfu/skills --skill antfu-issue-triage -g -a codex -y`
Cursor: `npx skills add antfu/skills --skill antfu-issue-triage -g -a cursor -y`
Gemini CLI: `npx skills add antfu/skills --skill antfu-issue-triage -g -a gemini-cli -y`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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 api` GET, `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-english` skill 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.

## Workflow

The rest: https://github.com/antfu/skills/blob/HEAD/skills/antfu-issue-triage/SKILL.md