docs-cleaner
- Repo stars 1,187
- Forks 185
- Author updated Jun 14, 2026, 10:01 AM
- Author repo claude-code-skills
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @daymade · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: docs-cleaner
description: Consolidates redundant documentation while preserving all valuable content. This skill should be…
category: other
runtime: no special runtime
---
# docs-cleaner output preview
## PART A: Task fit
- Use case: 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..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Core Principle / Workflow / Phase 1: Discovery” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “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.”.
- **02** When the source has headings, the agent prioritizes “Core Principle / Workflow / Phase 1: Discovery” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Start with a small task and check whether the result follows “Core Principle / Workflow / Phase 1: Discovery”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: docs-cleaner
description: Consolidates redundant documentation while preserving all valuable content. This skill should be…
category: other
source: daymade/claude-code-skills
---
# docs-cleaner
## When to use
- Consolidates redundant documentation while preserving all valuable content. This skill should be used when users want…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Core Principle / Workflow / Phase 1: Discovery” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "docs-cleaner" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Core Principle / Workflow / Phase 1: Discovery
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} 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
Decide Fit First
Design Intent
How To Use It
Boundaries And Review