Antfu Issue Triage

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

0. Resume. Look for earlier digests (gh issue list --state all --search "Triage digest in:title"). Read the one that matches this run (the unscoped digest for a full-repo run, the digest with the same focus for a focused run). If it exists: skip items already checked, re-check the unchecked ones, and scan only items newer than its recorded range plus items with new activity since its recorded date. Keep each item’s TASKxx code. If none matches, scan everything in scope. Also skim the other digests for codes already used and for items already tracked there (see Scoped digests).
1. Scope. Confirm the repo and range (default: all open items, narrowed by the digest if there is one; for large repos ask for a limit, label, or age filter). Fetch in bulk:

   bashCopy

   gh issue list --state open --limit 200 --json number,title,body,author,labels,createdAt,updatedAt,comments,reactionGroups,url,milestone
   gh pr list --state open --limit 200 --json number,title,body,author,labels,isDraft,reviewDecision,closingIssuesReferences,url,reactionGroups
   gh label list --limit 200 --json name,description

2. Learn the labels. Read every label name and description. Only apply labels that exist. New labels (including spam if missing) go in the Labels table and are created only after approval. Check how maintainers labeled similar items (gh issue list --state all --label <l>). Compare the repo’s labels with the Recommended Labels section below and note useful ones that are missing.
3. Map references. Collect cross-references from bodies, comments, and the timeline (gh api repos/{owner}/{repo}/issues/{n}/timeline --paginate): #123, URLs, closes/fixes, linked PRs, cross-repo links. Treat linked items as one cluster. Do not close an issue whose fix PR is still open. Do not mark linked items as duplicates of each other.
4. Check each item:
   • Already fixed/implemented. Search merged PRs and commits (gh pr list --state merged --search "<keywords>", git log -i --grep), changelog, docs, and current code. Find the first release with the fix (git tag --contains <sha> --sort=version:refname | head -1). Verify in the code, not just the title. A partial fix is not fixed: keep it open.
   • Duplicate. Group by symptom or request, not wording. Search open and closed issues with distinctive text (gh issue list --state all --search "<text>"). Pick one canonical item: linked PR > maintainer response > best repro > most reactions > oldest. Close the others into it.
   • Spam. Needs two or more strong signals: promo/SEO/crypto links, off-topic text, repeated identical posts, empty body with a link, bulk activity from a new account. Typos, terse text, wrong template, or non-English are not spam.
   • Labels. Suggest existing labels for unlabeled or mislabeled items.
   • Low hanging fruit. Items a maintainer can finish fast: PRs that are approved or ready with passing CI, small PRs with a clear change, typo or docs fixes, bugs with a clear repro and an obvious small fix, and requests that are small and well defined. Say why each is quick, and propose the low hanging fruit label for it. Skip items that are blocked, unclear, or large.
   • Status. For every item that is not closed in this run, record its digest marker now, while the evidence is fresh: 🚧 a PR is open for it, ❓ you could not decide, 🚨 security, ⚠️ extra notice (see Digest Issue for the full meaning), or none. Assign it a TASKxx code (reuse the code from the digest if it has one, otherwise the next unused number).
   • Demand. Count positive reactions (👍 ❤️ 🎉 🚀), negative ones, distinct commenters, “+1” comments, and folded-in duplicates. Rate High / Medium / Low for the repo’s size and show the raw numbers. Recent activity on an old item means it is still wanted.
5. Present the plan as the tables below, Stop to ask for confirmation. Run no write command in this turn.
6. Execute approved rows only, one at a time: comment, then label, then close. Stop on the first API error and report it. End with a done/failed table with links.
   • Run one issue per command (comment, label, and close for that issue chained with &&). Do not batch many issues in one script or loop: bulk write commands can be blocked by the permission classifier. If a command is blocked, do not work around it. Split it into smaller per-issue commands, and tell the user.
   • Create approved new labels first, in their own command.
   • For rows the user adds after the tables (for example “also close #4”), write a short fresh comment in the same style and show it in the final report.
7. Offer a digest issue. Ask whether to create or update the digest issue (see Digest Issue). It is built from the Needs attention rows, plus the items closed in this run. Do not write it without approval.

Recommended Labels

General labels. Map them to the repo’s existing labels first (same meaning, different name). Never rename or delete existing labels.

Rules:

• Keep every label’s description filled. If an existing label has none and its meaning is clear, suggest a description.
• Suggest only labels that would help this repo’s triage: needed by items you saw, or filling an obvious gap (for example no way to mark “needs reproduction” while many issues lack a repro). Do not suggest the whole list.
• Prefer a few feat: <area> labels backed by real clusters of issues over many speculative ones.
• Creating labels is a write action. List them in the Labels table (as (new label) rows) with name, color (match the repo’s palette), description, and the items that would use them. Create only after approval (gh label create <name> --description "..." --color <hex>), and before applying them to items.

Comments

Short, friendly, and specific. Examples of the tone (do not copy verbatim). Each ends with the notice on its own line:

• Fixed:

  mdCopy

  This was fixed in #456, released in v1.2.0. Please upgrade to get it. If it still happens, comment with a repro and we will reopen.
  
  🤖 *Automated by an agent.*

• Duplicate:

  mdCopy

  This is a duplicate of #123. Please follow that issue. Tell us if it is different and we will reopen.
  
  🤖 *Automated by an agent.*

• Spam:

  mdCopy

  Detected as a spam. Sorry if this was a mistake. Let us know and a maintainer can bring it back.
  
  🤖 *Automated by an agent.*

Rules per type:

• Fixed: link the PR or commit and release, and say what to do (upgrade, enable an option, use an API). Close as completed.
• Duplicate: name the canonical issue and invite the author to reopen if it differs. Close as not planned.
• Spam: add the spam label. Say it was detected as spam, with no reasoning. Say sorry if wrong, and say we can bring it back. Put the reasoning in the table, not in the comment. Close as not planned.

Action Tables

Three tables. Close and Labels rows are numbered so the user can reply “apply 1-5, skip 3”. Needs attention rows carry their TASKxx code instead, so the user can say “do TASK03” now and in later runs. Show the full comment text in the table.

1. Close

Reason is fixed, duplicate, or spam. Spam rows also add the spam label, and their reasoning stays in this table, not in the comment.

2. Labels

Include low hanging fruit rows here. For a label the repo does not have, add a row with item (new label), the name, description, color, and which items will use it. Approved new labels are created first (gh label create), then applied.

3. Needs attention (no write action)

Code is the TASKxx code and Status is the emoji marker (empty if none), both exactly as they will appear in the digest, so the digest is a copy of this table.

Put the most recommended check-them-first items at the top, ranked by importance: high demand, regressions or build-breaking bugs, security reports, security-sensitive or long-waiting PRs, and items with active unanswered discussion. Say why in Note. Low hanging fruits go here too, after those, with the reason it is quick.

Do not close PRs for being stale unless asked; label or flag them instead.

Digest Issue (optional)

After the actions are applied (or when the user only wants a report), offer to create a digest issue that records the Needs attention results, so later triage runs can pick up from it (Resume step). The digest is a copy of the Needs attention table; do not re-derive it. Creating an issue is a write action: ask first, show the full title and body, and create it only after approval. Skip the offer if the user declined or the list is empty.

• Title: Triage digest (YYYY-MM-DD), or Triage digest [<focus>] (YYYY-MM-DD) for a scoped digest (see Scoped digests). If an earlier digest with the same focus exists (gh issue list --state all --search "Triage digest in:title"), offer to update it (gh issue edit) instead of opening a new one, and keep checked items checked.
• Overview: start the body with a short Status paragraph (2-4 sentences): the overall state of open issues and PRs (rough counts, main themes or clusters, how healthy the backlog is, what is stale or blocked), then a Recommended start line naming the 1-3 items to do first and why.
• Items: one task-list line per item: - [ ] `TASK00` 🚧 #134 - <concise recommendation>. Mark items already handled as - [x]. Keep each line to one short sentence: what to do and why (for example review and merge, CI green, small change).
  • Code: every item gets a unique TASKxx code (TASK01, TASK02, … zero-padded, numbered in order of appearance) so the maintainer can say “do TASK03 and TASK07”. Codes are stable: when updating an existing digest, keep each item’s code, give new items the next unused number, and never reuse or renumber. Codes are unique across all digests of the repo, not per digest (see Scoped digests).
  • Link: the issue or PR reference (#134, or the full URL for another repo) right after the code and emoji.
  • Emoji: one status marker between the code and the link, or none if no marker applies:
    • ✅ done: already handled or fixed
    • 🚧 wip: a PR is open for it
    • ❓ unsure: the agent could not decide, needs a maintainer call
    • 🚨 security: security report or security-sensitive
    • ⚠️ extra notice: regression, breaking change, or anything else the maintainer should read first
    • Pick the most important one; omit the emoji otherwise (- [ ] `TASK04` #151 - ...).
• Groups: use these headings, in order, omitting empty ones:
  1. Prioritized - high demand, regressions, security, long-waiting items. Most important first.
  2. Low hanging fruit - quick wins, with the reason it is quick.
  3. Other - worth a look but neither urgent nor quick.
  4. Done in this run - items closed or fixed in this run, as - [x] lines with ✅ and their own code. A later run drops them once the digest has been updated again.
• Metadata: end the body with a block that lets a future run continue without redoing the scan:

  mdCopy

  ---
  - Focus: <"all", or the domain or feature, for example `router rewrite`>
  - Selection: <for a focus: how items were chosen, for example "label feat: router, keywords navigation/guard, cluster of #120">
  - Scanned: <repo>, open issues and PRs (<fetch filters used, or "all">)
  - Date: <YYYY-MM-DD>
  - Model: <model name or id>
  - Newest item scanned: #<n> (<createdAt>)
  - Counts: <n> issues, <n> PRs scanned; <n> closed, <n> labeled in this run

• Scoped digests: a scoped digest is a work list for one focus: a domain, feature, theme, or goal the maintainer is working on (router rewrite, SSR hydration, v2 release, Windows support). It is not a fetch filter. Fetch filters (limit, label, age for a large repo) only narrow what is scanned and go in the Scanned line; they do not make a scoped digest. Users can keep several scoped digests next to the full one.
  • The user names the focus. Pick the items by relevance across the whole backlog, not by one label: matching labels, keywords, the code area an item touches, and its reference cluster (linked issues and PRs). Include open PRs that implement the focus, and recently merged ones only when they explain an open item. Record how you chose in the Selection line, and list borderline items as ❓ rather than leaving them out silently.
  • Name the focus in the title and the Focus metadata line, using a short stable phrase. The same phrase is how the next run finds its digest, so reuse it exactly.
  • Order the groups for the focus, not the repo: what unblocks the focus first. Recommended start says what to do first for this focus. The Status paragraph describes the focus (its open work, blockers, how close it is), not the whole backlog.
  • A scoped digest only covers items in its focus. Never mark an item outside the focus as done or missing; the full digest, if any, stays untouched.
  • Codes are shared across the repo: before assigning a new code, read all digests (open and closed) and take the next number after the highest one used. If an item is already tracked in another digest, reuse its code instead of creating a second one, and add (also in #<digest>) to the line.
  • When the same item is checked off in one digest, mention it in the report so the user can tick it in the others; do not edit digests outside this run’s scope.
• Add the same 🤖 *Automated by an agent.* last line. Do not add labels or assignees unless asked.
• On the next run, follow the Resume step: the digest is read first, before scoping.