This skill should be used when the user asks about "garbage collection rules", "entropy fighting", "documentation staleness", "dead code detection", "convention drift", "periodic checks", "auto-fix rules", or needs guidance on the Garbage Collection section of HARNESS.md.
From ai-literacy-superpowersnpx claudepluginhub russmiles/ai-literacy-superpowers --plugin ai-literacy-superpowersThis skill uses the workspace's default tool permissions.
references/gc-catalogue.mdSearches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Garbage collection in a harness context means periodic checks that fight entropy — the slow drift that neither real-time hooks nor PR gates catch. Documentation goes stale, conventions erode, dead code accumulates, dependencies fall behind.
This is Boeckeler's third harness component: agents that run periodically to find inconsistencies and violations, actively fighting decay.
Every GC rule in HARNESS.md has five fields:
daily, weekly, or manualdeterministic or agenttrue (GC agent fixes it) or false (create an
issue instead)| Frequency | Use for |
|---|---|
| daily | Fast checks with high entropy rate (style drift in active codebases) |
| weekly | Most GC rules — documentation, dependencies, dead code |
| manual | Exploratory checks not yet calibrated for automation |
Start with weekly for most rules. Only move to daily if the entropy rate justifies the cost.
Auto-fix is safe when the fix is deterministic, local, verifiable, and reversible. It is not safe when the fix requires judgement, has ripple effects, cannot be verified, or is destructive.
For the full safety rubric and detailed examples, consult
references/gc-catalogue.md.
When auto-fix is true: The harness-gc agent applies the fix
directly (with user confirmation in interactive mode) and commits the
result.
When auto-fix is false: The agent creates a GitHub issue describing the finding, with file:line references and a suggested fix.
| Category | Examples | Typical frequency |
|---|---|---|
| Documentation entropy | Stale references, outdated versions | weekly |
| Convention drift | Naming violations, style drift | weekly |
| Dead code | Orphaned files, unused exports | weekly |
| Dependency entropy | Known CVEs, major version lag | weekly |
| Harness entropy | Missing tools, broken hooks | weekly |
For a full catalogue of GC patterns with HARNESS.md entry examples,
consult references/gc-catalogue.md.
references/gc-catalogue.md — Complete catalogue of common GC
patterns with HARNESS.md entry examples, detection approaches, and
the auto-fix safety rubric