skills.rest
phodal
phodalCOMMUNITY
Explore all skills by this author →
Website𝕏@phodal_huangGitHub

issue-garbage-collector

Scan duplicate and outdated issue files with Python and Claude.

1.8k|247|Updated Feb 16, 2026
Search Tags:#automation#python#cleanup#issues#scanning#harness#semantic-analysis
One-click install
npx skills add https://github.com/phodal/routa --skill issue-garbage-collector
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-garbage-collector
Source: https://github.com/phodal/routa/tree/main/.claude/skills/issue-garbage-collector
Command: npx skills add https://github.com/phodal/routa --skill issue-garbage-collector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Two-phase cleanup of duplicate and outdated issue files in docs/issues. Phase 1 uses a Python script for fast pattern matching to surface suspects; Phase 2 uses claude -p for semantic analysis on suspects only.

Core Features & Use Cases

  • Two-phase approach: fast surface with Python scanner, deep semantic review with Claude for suspect items.
  • Harness integration: connects with Harness automation for review and remediation.
  • Safe maintenance: preserves historical context while flagging duplicates, stale, and related issues for action.

Quick Start

Run the Python scanner to identify suspects and review the cleanup plan before applying changes.

Frequently Asked Questions about issue-garbage-collector

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

FAQPage Schema
How do I clean up duplicate and stale issues in my project tracker?▼

To clean up duplicate and stale issues, this Skill scans docs/issues with a Python script for fast pattern matching, then uses semantic analysis to confirm suspects and surface actionable consolidation steps.

How does semantic analysis work for finding outdated issue files?▼

Semantic analysis for outdated issue files works by applying Claude-based review only to suspects surfaced by the initial Python scanner, confirming duplicates and related issues while preserving historical context non-destructively.

What's the best way to automate issue consolidation across docs/issues?▼

The best way to automate issue consolidation across docs/issues is using a two-phase workflow: fast Python scanning for detection followed by Claude-based semantic review, integrated with Harness automation for remediation.

Can I use this issue scanning approach with Harness automation?▼

Yes, you can use this issue scanning approach with Harness automation, as the Skill explicitly provides harness integration to connect the two-phase review and remediation workflow with your automation pipeline.

Does the cleanup process delete historical issue files permanently?▼

No, the cleanup process does not delete issue files permanently; it implements non-destructive review to maintain history, flagging duplicates and stale issues for action while preserving the original context.

Related Skills

Explore More Software Engineering Skills→
onelee85onelee85

gsd-list-workspaces

Scan ~/gsd-workspaces for WORKSPACE.md manifests and summarize workspace statuses.

Community
Intermediate
AlamatorAlamator

issue-triage

Audit GitHub issues via gh CLI and draft validated triage actions.

Community
Advanced
harnessharness
80

configure-repo-scan

Insert code scanning steps into existing Harness pipeline YAML.

Official
Intermediate
haojing8312haojing8312
154

finding-duplicate-functions

Identify semantic duplicate functions in JavaScript/TypeScript codebases via extraction and LLM categorization.

Community
Intermediate