magpie-issue-triage
For each open `<issue-tracker>` issue in the configured candidate pool, read the issue body and comments and classify the candidate disposition. On user confirmation, posts a triage-proposal comment that invites the project team to react. Read-only on tracker state — no workflow transitions, closures, or label changes. Six classes in the body.
apache · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add apache/magpie --skill magpie-issue-triage技能说明
SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0
name: magpie-issue-triage
family: issue
mode: Triage
description: |
For each open <issue-tracker> issue in the configured
candidate pool, read the issue body and comments and classify
the candidate disposition. On user confirmation, posts a
triage-proposal comment that invites the project team to
react. Read-only on tracker state — no workflow transitions,
closures, or label changes. Six classes in the body.
when_to_use: |
Invoke when a project maintainer says "triage the issue
backlog", "groom recently filed issues", or "propose
dispositions for the unsorted queue". Also appropriate after
a batch import or as a periodic sweep on stale candidates.
Skip when team consensus has landed — invoke
/magpie-issue-fix-workflow for confirmed bugs or the appropriate
closure flow directly.
capability: capability:triage
license: Apache-2.0
issue-triage
This skill is the initial-triage discussion-starter for issues on the project's general issue tracker. For each open issue in the configured candidate pool, it reads the issue body and comments, applies the project's triage criteria, classifies the candidate disposition, and — on the user's explicit confirmation — posts a triage-proposal comment that invites the project team to react.
The skill never transitions workflow state, never closes, never assigns, never edits any tracker field. The disposition decision belongs to team consensus; this skill opens the discussion that produces it, and sibling skills apply the state change once consensus lands.
It composes with:
issue-reproducer— invoke when the classification depends on whether the reporter's code still fails on<default-branch>.issue-fix-workflow— invoke by hand after the team agrees a triaged issue is a confirmed bug or feature ready to fix.issue-reassess— sibling for sweep-mode work on the resolved or end-of-life pool (this skill handles the unsorted-new pool).
Golden rules
Golden rule 1 — read-only on tracker state. This skill posts discussion comments and nothing else. No workflow transitions, no label mutations, no body edits, no project-board column moves, no field changes. The skill's output is text on the tracker that invites reaction; the team's reply drives state change, applied later by sibling skills.
Golden rule 2 — every comment is a draft until the user
confirms. Triage proposals are public(-ish) comments on
<issue-tracker>, attributed to the maintainer who invoked the
skill. Per the "draft before send" rule in
AGENTS.md, every comment is drafted, shown to
the user, and posted only after explicit confirmation. The fact
that the user invoked the skill is not blanket authorisation —
the text of each comment is reviewed individually.
Golden rule 3 — six disposition classes, no more. The classification is a proposal, not a verdict; the team's reply may escalate or de-escalate. The skill always proposes exactly one class per issue — never two — because a two-class proposal stalls the discussion rather than starting it.
| Class | When to propose | Sibling skill / action |
|---|---|---|
BUG | Confirmed actionable bug; reproduces or has compelling evidence | /magpie-issue-fix-workflow |
FEATURE-REQUEST | Valid improvement or new-feature request; not a bug | Re-type as Improvement; route to project's roadmap |
NEEDS-INFO | Missing repro steps, environment, version, or other actionable detail | Request info from reporter |
DUPLICATE | Substantive overlap with an existing tracker issue (open or closed) | Link to canonical issue |
INVALID | By-design, won't-fix per project policy, out-of-scope, or environment-specific | Close with rationale |
ALREADY-FIXED | A commit on <default-branch> covers the report; the issue just needs closing | Close referencing the commit |
Golden rule 4 — never auto-escalate from a comment reply to a mutation. A reply on the tracker like "agreed, close it" is not authorisation for this skill to close the issue or transition state. The user types the next slash command explicitly; this skill's job ends at "comment posted".
Golden rule 5 — every issue / <upstream> reference is clickable
in the surface it lands on. Whenever this skill emits a reference
to an issue, PR, or comment — the proposal body, the action-items
list, the recap output — the reference must be one click away in
whatever surface it lands on:
-
On markdown surfaces (the proposal comment posted to
<issue-tracker>, any markdown-rendered action-items block): use the markdown link form perAGENTS.md§ Linking tracker issues and PRs:- Issue:
[<issue-tracker>#NNN](https://github.com/<issue-tracker>/issues/NNN) - PR:
[<upstream>#NNN](https://github.com/<upstream>/pull/NNN) - Comment: link to the
#issuecomment-<C>anchor.
- Issue:
-
On terminal surfaces (the pre-post proposal preview, the