skills.rest
nbramia
nbramiaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

stale

Identify stale pull requests, issues, branches, and plans in a repository.

20|4|Updated Jan 7, 2026
Search Tags:#github#cleanup#issues#branches#pull-requests#stale
One-click install
npx skills add https://github.com/nbramia/LifeOS --skill stale
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stale
Source: https://github.com/nbramia/LifeOS/tree/main/.agents/skills/stale
Command: npx skills add https://github.com/nbramia/LifeOS --skill stale

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Housekeeping report that identifies stale pull requests, issues, branches, and plans within a repository to guide cleanup.

Core Features & Use Cases

  • Stale PRs: Find open PRs not updated beyond a threshold.
  • Orphan branches: Detect local branches without an associated PR and track whether they are merged.
  • Stale issues: Highlight open issues that haven't been updated in a while.
  • Stale plans: Flag plan files in docs/plans not updated or completed.

Quick Start

Run the cleanup report for the current repository to surface actionable stale items.

Frequently Asked Questions about stale

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

FAQPage Schema
How do I find stale pull requests and issues in a GitHub repository?▼

Stale pull requests and issues are identified by querying GitHub via the gh CLI to find open items not updated beyond a specific threshold, generating a housekeeping report to guide repository cleanup.

What is the best way to detect orphan branches without an associated PR?▼

Detecting orphan branches involves inspecting local branches to find those without an associated pull request and tracking whether they have been merged, helping you safely remove abandoned work.

How do I identify stale plan files in my docs directory?▼

Identifying stale plan files is done by reading plan frontmatter in docs/plans to flag documentation that hasn't been updated or completed, ensuring your project planning stays current.

Can I use this stale item report for a codebase with multiple contributors?▼

Yes, this stale item report is designed for ongoing codebases with multiple contributors and documented planning, applying data retrieval and analysis to surface actionable cleanup tasks across the repository.

Related Skills

Explore More Software Engineering Skills→
shellicarshellicar

github-repos

Configure GitHub repository settings and enforce branch protection rules via the gh CLI.

Community
Intermediate
SteveFeldmanSteveFeldman
5

clean-branch

Categorize Git branches and generate a dry-run cleanup report.

Community
Intermediate
slamb2kslamb2k
5

start-right

Automate end-to-end repository initialization and scaffolding for new projects.

Community
Advanced
aeoncity-demoaeoncity-demo

builder-map

Monitor watched repositories for forks and builder announcements via GitHub API.

Community
Advanced