Docs Cleaner
- 757 installs
- 1.3k repo stars
- Updated August 4, 2026
- daymade/claude-code-skills
docs-cleaner is a Claude Code skill that systematically audits, condenses, and consolidates documentation for developers who need to eliminate duplication while preserving unique setup and troubleshooting content.
About
docs-cleaner is an Agent Skill from daymade/claude-code-skills that applies a value analysis template to project documentation section by section. Each section is scored for Keep, Delete, or Condense with line counts and reasons—for example keeping essential setup instructions while deleting content that duplicates CLAUDE.md. Developers reach for docs-cleaner when README sprawl, overlapping guides, or verbose technical sections make onboarding slow. The template tracks unique troubleshooting steps, frequently referenced procedures, and technical debt notes that must survive consolidation.
- Section-by-section value analysis using a keep/condense/delete framework
- 3-tier Value Categories: Keep (Green), Condense (Yellow), Delete (Red)
- Consolidation Checklist with 5 mandatory pre-deletion steps
- Outputs both a Value Analysis Table and a Consolidation Plan
- Maps overlaps across CLAUDE.md, README, and other project docs
Docs Cleaner by the numbers
- 757 all-time installs (skills.sh)
- Ranked #317 of 1,879 Documentation skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/daymade/claude-code-skills --skill docs-cleanerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 757 |
|---|---|
| repo stars | ★ 1.3k |
| Security audit | 3 / 3 scanners passed |
| Last updated | August 4, 2026 |
| Repository | daymade/claude-code-skills ↗ |
How do you consolidate duplicate project documentation?
Systematically audit, condense, and consolidate documentation while preserving unique value and eliminating duplication.
Who is it for?
Developers maintaining sprawling README or docs folders with overlapping CLAUDE.md, setup, and troubleshooting sections.
Skip if: Greenfield docs from scratch, auto-generated API reference only, or code refactoring unrelated to written documentation.
When should I use this skill?
The user asks to audit, deduplicate, condense, or clean up project documentation, README files, or CLAUDE.md overlaps.
What you get
Condensed documentation set, section value analysis table, and deduplicated guides preserving unique troubleshooting and setup content.
- Condensed documentation
- Value analysis table
- Deduplication report
By the numbers
- Uses a Document Analysis Table with Section, Lines, Value, and Reason columns
- Applies three value categories: Keep, Delete, and Condense
Files
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
1. Identify all documentation files covering the topic 2. Count total lines across files 3. 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
1. Create consolidated document with all valuable content 2. Delete redundant source files 3. Update references (CLAUDE.md, README, imports) 4. 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:
1. Consolidated document - Single source of truth 2. Value analysis - Section-by-section justification 3. Before/after metrics - Lines reduced, value preserved 4. Updated references - CLAUDE.md or README with pointer to new location
Security scan passed
Scanned at: 2026-06-13T19:44:41.856246
Tool: gitleaks + pattern-based validation
Content hash: 05162f259948be068f6d59cf0c66cf9971eb7b2fce92c8485b8332c80e440b49
Value Analysis Template
Use this template for section-by-section documentation analysis.
Document Analysis Table
| Section | Lines | Value | Reason |
|---|---|---|---|
| Example Section | 25 | Keep | Contains unique troubleshooting steps not documented elsewhere |
| Another Section | 40 | Delete | Duplicates content in CLAUDE.md |
| Technical Details | 60 | Condense | Valuable but verbose; can be reduced to 15 lines |
| Setup Instructions | 30 | Keep | Essential for onboarding |
Value Categories
Keep (Green)
- Unique information not found elsewhere
- Essential procedures (setup, troubleshooting, constraints)
- Frequently referenced content
- Technical debt / roadmap items
Condense (Yellow)
- Valuable but overly verbose
- Contains redundant examples
- Can be expressed more concisely
Delete (Red)
- Duplicates existing documentation
- One-time records (test results, meeting notes)
- Self-evident information (code already documents this)
- Outdated or superseded content
Consolidation Checklist
Before proposing deletions:
- [ ] Identified ALL files containing related content
- [ ] Mapped overlap between documents
- [ ] Listed unique value in each document
- [ ] Proposed single source of truth location
- [ ] Planned reference updates (CLAUDE.md, README, etc.)
Output Format
After analysis, produce:
1. Value Analysis Table - Per-section breakdown with keep/condense/delete 2. Consolidation Plan - Target structure with line count estimates 3. Before/After Comparison - Total lines and percentage reduction 4. Preserved Value Checklist - Confirm all valuable content retained
Related skills
Lark MarkdownInstantly turn any markdown file into clean, formatted Lark/Figma-compatible documents without manual reformatting.488k
Lark DocCreate, read, update, summarize, rewrite and manage Feishu/Lark cloud documents directly from agent workflows.401k16.1kLark WikiCreate, organize, query, and manage documents, spaces, and members inside Lark (Feishu) knowledge bases directly from AI agent workflows.397k16.1k
Domain ModelingBuild and sharpen a project's domain model: pin down domain terminology in a glossary and record architectural decisions as ADRs.318k202k
Opensource Guide CoachGet expert, attribution-safe guidance on launching and sustaining an open-source project.270k71Readme I18nMaintain consistent, updatable language selector blocks across every README variant in a multilingual repository.270k71How it compares
Pick docs-cleaner over generic writing skills when the task is auditing existing repo docs for duplication against CLAUDE.md and README overlap.
FAQ
How does docs-cleaner decide what to keep?
docs-cleaner labels each documentation section Keep, Delete, or Condense using a value analysis table with line counts and reasons. Unique troubleshooting, setup instructions, and frequently referenced content are kept; sections duplicating CLAUDE.md or other files are deleted.
What template does docs-cleaner use?
docs-cleaner uses a Document Analysis Table template with columns for Section, Lines, Value, and Reason. Developers apply Keep, Delete, and Condense categories to systematically reduce documentation sprawl while preserving essential procedures.
Is Docs Cleaner safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.