// Triage stale GitHub PRs. Use when asked to review old, inactive, least-recently-updated, obsolete, or closeable pull requests, comment with a recommendation, and close PRs that are clearly no longer useful.
Review Dependabot PRs updating Rust/Cargo crates with a security-focused crates.io tarball diff before commenting.
Review Dependabot PRs updating GitHub Actions workflows/actions, with a security-focused upstream diff check before commenting.
Must read before submitting PRs to Fedimint project
Use this skill when the user asks about Fedimint gateway liquidity management, lightning channels, gateway balances, routing fees, peg-in, peg-out, channel opening/closing, payment logs, invoices, or any gateway-cli operations. Triggers on: "gateway", "liquidity", "channels", "routing fees", "peg-in", "peg-out", "ecash balance", "lightning balance", "open channel", "close channel", "set fees", "payment summary", "invoice", "gateway-cli".
| name | github-stale-pr-triage |
| description | Triage stale GitHub PRs. Use when asked to review old, inactive, least-recently-updated, obsolete, or closeable pull requests, comment with a recommendation, and close PRs that are clearly no longer useful. |
Use this when asked to look through old open PRs and decide what should happen with them.
First find the exact PRs under consideration. Usually this means the least recently updated open PRs, filtered by the user's age cutoff:
gh pr list -R OWNER/REPO --state open --limit 20 \
--search 'updated:<YYYY-MM-DD sort:updated-asc' \
--json number,title,author,createdAt,updatedAt,isDraft,url,labels
For each PR, one by one:
Always write the analysis as a PR comment. Keep it polite and short. Say what you checked, what you concluded, and what the next step should be. If closing, say it can always be reopened if we missed something.
Close when it seems like the PR should be closed:
gh pr close NUMBER -R OWNER/REPO --comment-file /tmp/comment.md
Report back with a short table: PR, decision, action taken, rationale.