skills.rest
auerbachb
auerbachbCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pm-clean

Analyze GitHub open issues for inactivity, solved-by-PR, superseded, and duplicate closures.

3|1|Updated Feb 28, 2026
Search Tags:#github#cleanup#review#backlog#issues#inactive
One-click install
npx skills add https://github.com/auerbachb/claude-code-config --skill pm-clean
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-clean
Source: https://github.com/auerbachb/claude-code-config/tree/main/.claude/skills/pm-clean
Command: npx skills add https://github.com/auerbachb/claude-code-config --skill pm-clean

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scan open issues for staleness and present non-destructive closure recommendations. Detects issues solved by merged PRs, no-activity issues (30+ days), superseded issues, and potential duplicates of already-closed issues. Presents recommendations for user confirmation — never auto-closes. Triggers on "pm-clean", "stale issues", "clean backlog", "close stale".

Core Features & Use Cases

  • Detect stale issues and surface closures without auto-closing.
  • Cross-reference merged PRs to flag solved-by-pr relationships.
  • Flag inactive, superseded, and potential duplicates for reviewer confirmation.
  • Works on GitHub project backlogs with configurable inactivity thresholds and reporting.

Quick Start

Initiate a backlog cleanup scan for open issues and review the generated recommendations.

Frequently Asked Questions about pm-clean

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

FAQPage Schema
How do I clean up a GitHub backlog of stale issues?▼

You can scan your GitHub backlog for stale issues by analyzing open issues for 30+ days of inactivity, solved-by-PR relationships, and duplicates to surface actionable closure recommendations without auto-closing.

How do I find GitHub issues already solved by merged pull requests?▼

Finding GitHub issues solved by merged pull requests involves cross-referencing open issues against historical merged PR activity to flag solved-by-PR relationships for reviewer confirmation.

What is the best way to identify duplicate issues in a GitHub repository?▼

Identifying duplicate issues in a GitHub repository requires comparing open issues against already-closed items to surface potential duplicates for reviewer confirmation.

Does backlog cleanup automatically close inactive GitHub issues?▼

No, backlog cleanup does not automatically close inactive GitHub issues; it applies threshold-based inactivity checks and presents categorized recommendations strictly for user confirmation.

Can I configure the inactivity threshold for detecting stale GitHub issues?▼

Yes, you can configure the inactivity threshold for detecting stale GitHub issues, applying custom day-count limits to identify inactive items and generate tailored backlog reporting.

Related Skills

Explore More Product & Management Skills→
FriendlyInternetFriendlyInternet
10

epic-digest

Generate daily GitHub epic summaries with status, progress, and blockers.

Official
Advanced
aditriokaaditrioka

audit-burndown

Automate auditing and burndown of backlog items with task routing.

Community
Advanced
adeboldadebold

github-project-management

Orchestrate swarm-coordinated GitHub issue management and project-board automation.

Community
Intermediate
OGismatulinOGismatulin

github-issue-triage

Classify, label, and close GitHub issues for backlog management.

Community
Intermediate