magpie-issue-stale-sweep
Sweep open `<issue-tracker>` issues for inactivity past a configurable threshold and propose either a closure (when the issue has been unresponsive long enough to presume abandonment) or an update request (nudge the reporter to confirm the issue is still relevant). Waits for maintainer confirmation before posting any comment or closing anything.
apache · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add apache/magpie --skill magpie-issue-stale-sweep技能说明
SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0
name: magpie-issue-stale-sweep
family: issue
mode: Triage
description: |
Sweep open <issue-tracker> issues for inactivity past a
configurable threshold and propose either a closure (when the
issue has been unresponsive long enough to presume abandonment) or
an update request (nudge the reporter to confirm the issue is still
relevant). Waits for maintainer confirmation before posting any
comment or closing anything.
when_to_use: |
Invoke when a maintainer says "sweep stale issues", "close stale
issues", "nudge reporters on old issues", or "find issues with no
activity for N days". Also appropriate as a periodic backlog-hygiene
pass or before a major release cut to reduce open-issue noise. Skip
when the goal is to reassess resolved / EOL issues — use
issue-reassess for that — or when the tracker already has its own
automated stale bot configured and the maintainer wants to manage it
through that instead.
capability: capability:triage
license: Apache-2.0
issue-stale-sweep
This skill is the stale-issue sweep for the project's general issue
tracker. It identifies open issues that have had no new comment or update
activity past a configurable inactivity threshold, classifies each as
either REQUEST-UPDATE or CLOSE-STALE, and — on the user's explicit
confirmation — posts one lightweight comment per issue (a nudge or a
pre-close notice, as appropriate).
The skill never closes, labels, transitions, or edits any tracker field without confirmation. The decision belongs to the maintainer; this skill surfaces the candidates and pre-drafts the comments so the maintainer can review in bulk and confirm or skip individually.
It composes with:
issue-triage— the main triage skill for unsorted-new issues; stale-sweep is the hygiene pass for the open-but- dormant pool.issue-reassess— for the resolved / EOL pool (stale-sweep handles the still-open dormant pool instead).
Disposition vocabulary
The skill uses exactly two disposition classes:
| Class | When to propose | Follow-up action |
|---|---|---|
REQUEST-UPDATE | Issue is dormant past the warn threshold but not yet past the close threshold; reporter has not recently responded | Post a nudge comment asking the reporter to confirm the issue is still relevant on the current <default-branch>; no state change yet |
CLOSE-STALE | Issue is dormant past the close threshold and has already received a REQUEST-UPDATE nudge with no response, or is dormant past a hard-close threshold with no nudge needed | Post a pre-close notice and, on a second explicit confirmation, close the issue |
The two thresholds (warn_days and close_days) default to the values in
<project-config>/stale-sweep-config.md
when that file exists, or to framework defaults (90 / 180 days) when it
does not. The user may override either threshold inline at invocation time.
Golden rules
Golden rule 1 — read-only on tracker state until confirmed. This skill posts comments and closes issues only after the user confirms each action individually. No label mutations, no workflow transitions, no body edits, no project-board column moves. Every post and every close is proposed, shown, and executed only after the user says "yes" for that specific item.
Golden rule 2 — every comment is a draft until confirmed. Per the
"draft before send" rule in AGENTS.md, every comment
body is drafted and shown before posting. The fact that the user invoked
the skill is not blanket authorisation — each comment is reviewed
individually. Closures require a second explicit confirmation step after
the comment has posted.
Golden rule 3 — two classes, no more. The classification is either
REQUEST-UPDATE or CLOSE-STALE. No hybrid or escalation proposals in a
single comment.
Golden rule 4 — never close without a posted nudge first (unless the
hard-close threshold applies). An issue that has never received a
stale-sweep nudge in this tracker must receive a REQUEST-UPDATE comment
first, wait the warn-to-close window, and only then be eligible for
CLOSE-STALE. The exception is the configurable hard_close_days
threshold (default: 365 days) where a nudge is skipped for exceptionally
dormant issues.
Golden rule 5 — every issue / <upstream> reference is clickable in
the surface it lands on. Whenever this skill emits a reference to an
issue — the proposal body, the confirmation screen, the recap — it must be
one click away in whatever surface it lands on:
-
On markdown surfaces (comment body posted to
<issue-tracker>, confirmation-screen preview): use the markdown link form perAGENTS.md§ Linking tracker issues and PRs:[<issue-tracker>#NNN](https://github.com/<issue-tracker>/issues/NNN). -
On terminal surfaces (the pre-post preview, the recap): wrap the visible short form in OSC 8 hyperlink escape sequences (`\e]8;;\e\\e]8;;\e\