Docs Cleaner

This does what every codebase eventually needs: turns three redundant docs into one without losing anything important. It works through a structured four-phase process, mapping overlaps, analyzing each section for unique value (keep/condense/delete), then consolidating into a single source of truth. The standout feature is the value analysis table that forces you to justify why each section stays or goes, which prevents the usual problem of either deleting too much or chickening out and keeping everything. Best used when you've got 500+ lines spread across multiple files all explaining the same thing. The workflow is methodical enough that you won't regret deletions later.

skills.sh installs: 1K
GitHub stars: 1.5K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add daymade/claude-code-skills --skill docs-cleaner --agent claude-code

Installs into .claude/skills of the current project.

Files

Docs Cleaner

Documentation goes wrong in recurring ways, and they need different work.

It rots. Something changed — a port, a path, a procedure, a decision — and the docs still describe the old world. The field's name for this is documentation rot or version drift: artifacts fall out of sync one at a time until people stop trusting the set.

It sprawls. The same topic accumulates three files, each partly right, none authoritative.

They trace to one root cause: a fact was written down in more places than it was defined. Everything below follows from fixing that.

Core principle (governs both modes)

Critical evaluation before deletion. Never blindly delete. Analyze each section's unique value before proposing removal. The goal is reduction without information loss.

This governs every deletion-shaped action in this skill, not just consolidation: archiving a document, dropping a derived value, and removing a cross-reference are all deletions and all owe the same analysis first. "It looked redundant" is not that analysis.