github-stale-issues-triage

Reviews stale GitHub issues, comments with triage findings, and closes resolved ones.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Open issue backlogs accumulate stale, obsolete, or already-completed items that hide real work. This Skill systematically reviews the least-recently-updated issues, researches each one against the current codebase, and either closes it or leaves a documented triage comment. ## Core Features & Use Cases - Stale Issue Identification: Selects the least-recently-updated open issues, optionally filtered by count or age cutoff. - Evidence-Based Research: Reads issue bodies and comments, then checks current code, documentation, tests, and related issues/PRs before judging relevance. - Conservative Closure Policy: Closes only issues that are clearly done, invalid, or obsolete, and always posts a concise triage comment explaining the decision. - Use Case: A maintainer asks to review the 20 oldest open issues; the Skill investigates each one, comments with findings, closes three that are already fixed, and returns a summary table of decisions and rationale. ## Quick Start Review the 15 least-recently-updated open issues in this repository, comment on each with your findings, and close any that are clearly done or obsolete.

Frequently Asked Questions about github-stale-issues-triage

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

FAQPage Schema
How do I triage stale GitHub issues automatically?

Select the least-recently-updated open issues, read each issue and its comments, then verify against current code, docs, and tests. Post a short comment with your judgment on every issue and close only those that are clearly done or obsolete.

How to decide whether an old GitHub issue should be closed?

Research the issue against the current codebase, documentation, tests, and related PRs to classify it as still relevant, partially done, already done, obsolete, or unclear. Close only when the conclusion is unambiguous; otherwise leave it open with a triage comment.

Should I comment on stale issues even when leaving them open?

Yes. Always post a short comment describing what you checked and your judgment, even when keeping the issue open. This intentionally bumps stale issues with useful triage context for maintainers.

When should stale issues not be closed during triage?

Do not close issues that are ambiguous, partially done with remaining scope, or needing maintainer or product input. Conservative triage leaves uncertain issues open and avoids changing labels or assignees unless explicitly requested.

Can stale issue triage be delegated to sub-agents?

Yes. When the batch is large or issues are independent, individual issues can be delegated to sub-agents for parallel research, with results consolidated into a summary table of decisions and rationale.