garbage-collector

Scan repositories to identify dead code, TODOs, duplicate filenames, and oversized files.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/matthabermehl/generation-b-kids-books --skill garbage-collector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: garbage-collector
Source: https://github.com/matthabermehl/generation-b-kids-books/tree/main/.codex/skills/garbage-collector
Command: npx skills add https://github.com/matthabermehl/generation-b-kids-books --skill garbage-collector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python, and includes scripts (resource) components.

What problem does it solve?

This Skill helps reduce repository entropy by locating dead code, TODO/FIXME hotspots, duplicate utilities, inconsistent naming, and large unwanted files so maintainers can make small, safe cleanup commits that preserve behavior.

Core Features & Use Cases

  • Heuristic quick-scan script to list largest files, TODO/FIXME occurrences, and duplicate-ish filenames to prioritize cleanup.
  • Guidance and checklist for producing small, reviewable refactor or deletion commits and for quarantining flaky tests.
  • Use case: run a scan before a cleanup sprint to create targeted PRs that remove duplicated helpers, clarify scripts, and reduce agent confusion.

Quick Start

Run the garbage-collector scan to generate a list of hotspots and propose small cleanup actions.

Frequently Asked Questions about garbage-collector

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

FAQPage Schema
How do I find dead code and TODO hotspots in my repository?

You can locate duplicate utilities and oversized files by running a portable quick-scan script that detects duplicate-ish filenames and lists the largest files, helping you prioritize cleanup targets for small, safe refactor commits.

How do I reduce repository entropy without breaking existing behavior?

Reduce repository entropy by performing a non-destructive scan that generates actionable, reviewable suggestions for cleanup targets, allowing maintainers to make small, safe deletion commits that preserve codebase behavior.

What is the best way to prepare for a codebase cleanup sprint?

The best way to prepare for a cleanup sprint is to run a repository scan that produces a prioritized list of maintenance drift, flaky tests, and noisy TODOs, enabling you to create targeted PRs for codebase simplification.

Does this repository maintenance tool require Python to run?

Python is required to run the repository maintenance scan, as the portable quick-scan script prefers Python when available to detect duplicate utilities and dead code in your codebase or monorepo.

Can I scan a monorepo for duplicate helpers and flaky tests?

Yes, you can scan a monorepo for duplicate helpers and flaky tests; the scan applies to codebases where maintenance drift and duplicated utilities hinder developer workflows and CI reliability.