issue-stale-sweep

Identify inactive issues and propose closing actions in an issue tracker.

79|76|Updated Apr 28, 2026

Search Tags:#issue tracker #issue management #triage #project maintenance #stale issue

Ready to run

npx skills add https://github.com/apache/magpie --skill issue-stale-sweep

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issue-stale-sweep
Source: https://github.com/apache/magpie/tree/main/skills/issue-stale-sweep
Command: npx skills add https://github.com/apache/magpie --skill issue-stale-sweep

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The issue-stale-sweep skill simplifies the process of identifying and managing inactive issues in your project's issue tracker, helping to keep the issue backlog tidy and maintainable.

Core Features & Use Cases

Stale Issue Detection: Identifies open issues that have not had activity for a specified period.
Issue Management: Proposes actions to maintain the issue tracker, such as updating or closing stale issues.
User Confirmation: Requires user confirmation before making any changes to issue states.
Use Case: Before a major release, use the issue-stale-sweep skill to remove noise from the issue tracker by addressing issues that have been inactive for a long time.

Quick Start

Run the issue-stale-sweep skill to sweep for stale issues in your tracker.

Frequently Asked Questions about issue-stale-sweep

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

FAQPage Schema

How do I automate stale issue management in my project tracker?▼

Automate stale issue management by running a sweep to identify inactive issues based on a specified period of inactivity and proposing actions like closing them. It requires issue tracker read and write access and user confirmation before applying any state changes.

What is stale issue detection and when do I need it for project maintenance?▼

Stale issue detection identifies open tracker issues lacking recent activity. You need it for project maintenance before major releases to clean up the backlog, remove noise, and keep your issue tracker tidy and maintainable.

Does the stale issue sweep automatically close inactive issues without permission?▼

No, the stale issue sweep requires user confirmation before making any changes to issue states. It proposes management actions for inactive issues but relies on your explicit approval to execute closing or updating operations.

Do I need special permissions to run a stale issue triage?▼

Yes, you need issue tracker read and write access to run stale issue triage. The skill also leverages project configuration files to determine the specified inactivity period and apply proposed management actions.

What's the best way to clean up an issue backlog before a major release?▼

The best way to clean up an issue backlog is running an automated sweep for inactive issues, proposing updates or closures for long-inactive items, and confirming changes to remove tracker noise and maintain a tidy backlog.