- Home
- Skills
- Daymade
- Claude Code Skills
- Docs Cleaner
docs-cleaner_skill
- Python
609
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill daymade/claude-code-skills --skill docs-cleaner- .security-scan-passed181 B
- SKILL.md2.9 KB
Overview
This skill consolidates redundant documentation while preserving all valuable content. It reduces documentation sprawl by merging overlapping files into a single authoritative document and producing a clear justification for every change. Use it to shrink doc volume without losing essential procedures, constraints, or troubleshooting guidance.
How this skill works
The skill scans a set of documentation files, counts lines, and maps overlap to identify redundancy. It produces a section-by-section value analysis (Keep, Condense, Delete), a consolidation plan with before/after metrics, and a consolidated document that retains 100% of valuable information. Finally, it updates references and verifies no broken links remain.
When to use it
- When documentation exceeds ~500 lines across multiple files on the same topic
- When you hear triggers like “clean up docs”, “consolidate documentation”, or “merge these docs”
- When multiple files create conflicting or duplicate guidance
- When onboarding or maintenance is slowed by doc sprawl
- When you need a single source of truth for a component or feature
Best practices
- Perform a section-by-section value analysis before any deletion
- Categorize content as Keep, Condense, or Delete with explicit reasons
- Preserve all essential procedures, constraints, and troubleshooting items
- Create clear before/after metrics and store the value analysis alongside the consolidated doc
- Update all references and verify links to avoid orphaned pointers
- Keep one authoritative file and add short pointers for historical records
Example use cases
- Merge three overlapping setup guides into one concise setup & troubleshooting document
- Condense verbose API reference files into a compact reference with preserved examples
- Remove one-time test reports while preserving test patterns and expected outputs
- Consolidate multiple HOWTOs into a single workflow with per-step rationale and gotchas
- Reduce onboarding docs from many files into a single quickstart plus deeper reference
FAQ
Every section gets a documented value analysis with explicit reasons. Items marked Delete are reviewed for one-time or outdated status and preserved elsewhere if needed.
Will links and imports break after consolidation?
No—updating references is part of execution. The skill verifies links and updates in-project pointers to the consolidated document.
Can I keep historical files for audit?
Yes. The plan can archive original files with pointers rather than immediate deletion, maintaining traceability while reducing active documentation.