github-stale-pr-triage

Reviews stale GitHub pull requests, comments with recommendations, and closes obsolete ones.

78|27|Updated May 4, 2024
One-click install
npx skills add https://github.com/fedixyz/fedi --skill github-stale-pr-triage-fedixyz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-stale-pr-triage
Source: https://github.com/fedixyz/fedi/tree/main/.agents/skills/github-stale-pr-triage
Command: npx skills add https://github.com/fedixyz/fedi --skill github-stale-pr-triage-fedixyz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Open pull requests accumulate over time, leaving maintainers unsure which ones are still relevant, which are obsolete, and which deserve a decision. This Skill automates the review of old, inactive PRs so backlogs stay clean without manual archaeology. ## Core Features & Use Cases - Stale PR Identification: Filters open PRs by age cutoff, count, labels, author, or least-recently-updated order. - Per-PR Analysis: Reads each PR's description, discussion, reviews, changed files, and diff, then checks current code and related issues to determine if the work is still needed. - Decision and Action: Comments with a polite recommendation on every PR and closes those that are clearly obsolete, superseded, or would need a rewrite. - Use Case: A maintainer asks to triage all PRs untouched for 6 months. The Skill reviews each one, posts a short analysis comment, closes the dead ones, and returns a summary table of PR, decision, action, and rationale. ## Quick Start Review the 20 least-recently-updated open pull requests in this repository, comment with a recommendation on each, and close any that are clearly obsolete.

Frequently Asked Questions about github-stale-pr-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage stale pull requests on GitHub?

Filter open PRs by age cutoff, labels, author, or least-recently-updated order, then review each PR's description, discussion, reviews, and diff. Check whether the work is still needed in current code, comment with a recommendation, and close PRs that are clearly obsolete or superseded.

How to decide whether an old pull request should be closed?

Close a PR when it is obsolete, irrelevant, already implemented another way, or would need a fresh rewrite. Leave it open if it is still useful and easy to finish, or leave it open with a clear question when the answer is genuinely unclear.

Can stale PR triage be delegated to sub-agents?

Yes, each PR can be delegated to a self-contained sub-agent for independent analysis. This parallelizes the review of large backlogs while keeping each PR's investigation isolated and focused.

What should a stale PR triage comment include?

Keep the comment polite and short: state what was checked, what conclusion was reached, and what the next step should be. If closing the PR, note that it can always be reopened if something was missed.

When should an old pull request not be closed?

Do not close a PR when the work is still relevant and looks easy to finish, or when the correct decision is genuinely unclear. In unclear cases, leave the PR open with a specific question for the author or maintainers.