skills.rest
jonaseck2
jonaseck2COMMUNITY
Explore all skills by this author →
GitHub

oss-stale

Closes GitHub issues and pull requests inactive for 60+ days.

2|Updated Apr 2, 2026
Search Tags:#github#pull requests#issue triage#repository maintenance#stale cleanup#automated closing#contributor communication
One-click install
npx skills add https://github.com/jonaseck2/slaktforskning --skill oss-stale
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: oss-stale
Source: https://github.com/jonaseck2/slaktforskning/tree/main/.claude/skills/oss-stale
Command: npx skills add https://github.com/jonaseck2/slaktforskning --skill oss-stale

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you close GitHub issues and pull requests that have been inactive for a long time, reducing clutter and keeping triage focused.

Core Features & Use Cases

  • Find stale issues and PRs: Identifies open items with no activity for 60+ days while skipping items already labeled stale.
  • Explain and close: Posts a clear comment before closing so contributors understand why the item was finalized.
  • Handle PR drafts with caution: Avoids closing draft PRs unless they are older than 90 days, reducing accidental shutdowns of active work.

Quick Start

Tell the AI to run the stale cleanup for your repository by closing open issues and PRs that have had no activity for 60+ days, commenting first and keeping draft PRs open unless they exceed 90 days.

Frequently Asked Questions about oss-stale

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

FAQPage Schema
How do I automatically close inactive GitHub issues and pull requests?▼

To automatically close inactive GitHub issues and pull requests, this Skill identifies open items with no activity for 60+ days, posts an explanatory comment for contributors, and closes them while reporting final counts.

How does stale issue triage handle pull requests that are drafts?▼

Stale issue triage handles draft pull requests cautiously by keeping them open unless they exceed 90 days of inactivity, preventing accidental shutdowns of active work while still cleaning up long-abandoned drafts.

Can I skip GitHub issues that already have a stale label during repository cleanup?▼

Yes, you can skip GitHub issues that already have a stale label during repository cleanup. This Skill specifically excludes items already labeled stale to avoid redundant processing and duplicate notifications.

What is the best way to communicate issue closure reasons to contributors?▼

The best way to communicate issue closure reasons to contributors is by posting a clear comment before finalizing. This Skill automatically adds an explanatory message to each inactive item so contributors understand why it was closed.

Does automated stale cleanup work with the GitHub CLI for repository maintenance?▼

Yes, automated stale cleanup works with the GitHub CLI for repository maintenance. It calculates a cutoff date, lists candidate items via GitHub CLI queries, and processes closures directly within your triage workflow.

Related Skills

Explore More Product & Management Skills→
rafrusthrafrusth
2

summarize-activity

Summarize recent GitHub activity into a markdown report with clickable links.

Community
Advanced
swarm-ai-researchswarm-ai-research

Janitor

Delete stale .notify-* files, .pending-notify-temp/ artifacts, and .outputs/ chain artifacts by TTL.

Official
Intermediate
C0ntr0lledCha0sC0ntr0lledCha0s
8

github-issues

Triage GitHub issues for Logseq Template Graph with validation and labeling.

Community
Intermediate
redhat-best-practices-for-k8sredhat-best-practices-for-k8s

fix-stale-issues

Remove lifecycle/stale labels from linked telco-bot tracking issues via GitHub comments.

Official
Intermediate