docs-cleaner
Consolidates redundant documentation while preserving all valuable content. This skill should be used when users want to clean up documentation bloat, merge redundant docs, reduce documentation sprawl, or consolidate multiple files covering the same topic. Triggers include "clean up docs", "consolidate documentation", "too many doc files", "merge these docs", or when documentation exceeds 500 lines across multiple files covering similar topics.
pinned to #029876dupdated last month
Ask your AI client: “install skills/docs-cleaner”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/docs-cleanermetahub onboarded this repo on the author's behalf.
If you own github.com/daymade/claude-code-skills on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
1,331
Last commit
last month
Latest release
published
About this skill
Pulled from SKILL.md at publish time.
Consolidate redundant documentation while preserving 100% of valuable content.
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.029876d· last month
Behavioral checks ran but aren't published for this artifact; the static checks above ran at publish time.
Documentation
7 passed2 warningsTags / topics declaredwarn
No manifest tags and no GitHub repo topics
Add tags to the manifest (or GitHub topics on the repo) so the registry's search and category filters surface this artifact.
Homepage or repository declaredwarn
No homepage or repository declared.
Add a "homepage" or "repository" field to SKILL.md.
Description quality
61 words · 448 chars — "Consolidates redundant documentation while preserving all valuable content. This…"
README is present and substantial
182,381 chars · 15 sections · 88 code blocks
README has usage / example sections
found: Example
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking
Description is substantive
Description is 61 words.
Documentation present and substantive
Documentation present (SKILL.md, 425 words).
Documentation shows usage
Documentation includes 1 code example.
Release history
1- releasecurrent029876dwarnlast month
Contents
Documentation Cleaner
Consolidate redundant documentation while preserving 100% of valuable content.
Core Principle
Critical evaluation before deletion. Never blindly delete. Analyze each section's unique value before proposing removal. The goal is reduction without information loss.
Workflow
Phase 1: Discovery
- Identify all documentation files covering the topic
- Count total lines across files
- Map content overlap between documents
Phase 2: Value Analysis
For each document, create a section-by-section analysis table:
| Section | Lines | Value | Reason |
|---|---|---|---|
| API Reference | 25 | Keep | Unique endpoint documentation |
| Setup Steps | 40 | Condense | Verbose but essential |
| Test Results | 30 | Delete | One-time record, not reference |
Value categories:
- Keep: Unique, essential, frequently referenced
- Condense: Valuable but verbose
- Delete: Duplicate, one-time, self-evident, outdated
See references/value_analysis_template.md for detailed criteria.
Phase 3: Consolidation Plan
Propose target structure:
Before: 726 lines (3 files, high redundancy)
After: ~100 lines (1 file + reference in CLAUDE.md)
Reduction: 86%
Value preserved: 100%
Phase 4: Execution
- Create consolidated document with all valuable content
- Delete redundant source files
- Update references (CLAUDE.md, README, imports)
- Verify no broken links
Value Preservation Checklist
Before finalizing, confirm preservation of:
- Essential procedures (setup, configuration)
- Key constraints and gotchas
- Troubleshooting guides
- Technical debt / roadmap items
- External links and references
- Debug tips and code snippets
Anti-Patterns
| Pattern | Problem | Solution |
|---|---|---|
| Blind deletion | Loses valuable information | Section-by-section analysis first |
| Keeping everything | No reduction achieved | Apply value criteria strictly |
| Multiple sources of truth | Future divergence | Single authoritative location |
| Orphaned references | Broken links | Update all references after consolidation |
Output Artifacts
A successful cleanup produces:
- Consolidated document - Single source of truth
- Value analysis - Section-by-section justification
- Before/after metrics - Lines reduced, value preserved
- Updated references - CLAUDE.md or README with pointer to new location
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/docs-cleaner