Agent skill · writing content · daymade
docs-cleaner
Consolidates redundant documentation while preserving all valuable content; keeps a doc set truthful after things change. Modes: (1) POST-CHANGE GOVERNANCE — when code, scripts, config, env vars, ports, paths, deployment, auth, tests, or a documented procedure changed; also "which docs are now wrong", "check docs for inconsistencies", "过时的命令/路径", "文档同步". Use it even when the user mentions only the change and never the docs — updating them is part of the change, not optional cleanup. (2) CONSOLIDATION — "clean up docs", "documentation bloat", "reduce documentation sprawl", "consolidate documentation", "too many doc files", "merge redundant docs", "merge these docs", "文档太多/太乱", multiple files covering the same topic, or documentation exceeding 500 lines across multiple files on similar topics. Finds stale copies of a fact changed in only one place, values that should never have been persisted (counts, totals, "N items", restated summaries), rival definitions that drift apart, and orphaned cross-references.
Why this skill is useful
Provides a structured methodology for consolidating documentation that includes specific evaluation criteria and templates not commonly found in general resources.
What it needs
About 13k tokens when loaded. Last updated 2026-08-07. 1,320 stars on the source repository.
What this skill does
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. Which mode are you in? The user said / the situation Mode --- --- "I changed X" / a diff exists / a procedure was updated 1 — Post-change governance "which docs are now wrong", "check for stale commands/paths" 1 — Post-change governance "clean up the docs", "too many files on this", "merge these" 2 — Consolidation A topic is spread over several files with no clear owner 2 — Consolidation They share the Drift Test below. When both apply, run Mode 1 first: consolidating docs that are also factually stale just produces one confidently wrong document. A note on CLAUDE.md / AGENTS.md: both modes apply to them like any other document — govern them after a change, consolidate them when they duplicate each other. The one job that belongs elsewhere is restructuring a single oversized one — pushing low-frequency detail down into references while keeping the top level lean. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills daymade/docs-cleaner