菜单
Remove historical cruft from design docs. Use when docs accumulate outdated content, after major refactorings, or when preparing for releases.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | design-prune |
| description | Remove historical cruft from design docs. Use when docs accumulate outdated content, after major refactorings, or when preparing for releases. |
| allowed-tools | Read, Edit, Glob, Bash(grep *), Bash(date *) |
| context | fork |
| agent | design-doc-agent |
Removes historical cruft from design documentation by detecting and removing outdated content, update histories, and deprecated sections while preserving essential historical context.
This skill cleans up design documentation by identifying historical content patterns, calculating staleness scores, generating pruning plans, and applying safe removal strategies to keep docs focused on current state while preserving important context.
Basic pruning:
/design-docs:design-prune effect-type-registry
Aggressive pruning:
/design-docs:design-prune effect-type-registry --aggressive
Dry-run (preview only):
/design-docs:design-prune effect-type-registry --dry-run
module: Module name to prune (or "all" for all modules)doc: Specific document to prune (default: all docs in module)aggressive: Remove all historical content (default: false, conservative mode)dry-run: Preview changes without applying (default: false)High-level pruning process:
For detailed implementation steps, see supporting documentation below.
When you need detailed information, load the appropriate supporting file:
See instructions.md for:
Load when: Performing pruning or need implementation details
See pruning-strategies.md for:
Load when: Need strategy details or deciding which approach to use
See content-patterns.md for:
Load when: Detecting historical content or understanding pattern matching
See examples.md for:
Load when: User needs examples or clarification
INFO: No historical content detected
Document: {doc}
All content appears current.
No pruning needed.
WARNING: Pruning would remove >50% of content
Document: {doc}
Removal: {percentage}%
Suggestion: Review document - consider if it should be archived entirely
or switch to conservative mode.
ERROR: Pruning would break cross-references
Section: {section}
Referenced by: {other-docs}
Action: Preserved section to maintain references.
Update referencing docs before pruning.
Works well with:
/design-docs:design-sync - Sync docs before pruning to ensure currency/design-docs:design-review - Identify documents needing pruning/design-docs:design-validate - Validate after pruning/design-docs:design-archive - Archive documents that are mostly historicalA successful pruning:
Generate cross-reference graph showing relationships between design documents. Use when visualizing doc dependencies, finding related docs, or understanding documentation structure.
Validate design doc structure and frontmatter. Use when checking design docs for compliance, ensuring proper formatting, or verifying metadata before commits.
Comprehensive quality audit for CLAUDE.md context files. Use when performing thorough quality checks, preparing for releases, ensuring context efficiency, or verifying token optimization.
Style rules for LLM context files (CLAUDE.md, AGENTS.md and their .local variants). Fires automatically when these files are opened. Enforces on-demand loading patterns, proper @-reference syntax and lean context structure.
Split large CLAUDE.md into child files. Use when context files exceed word limits, are too verbose, or cover multiple distinct topics that should be separate.
Validate CLAUDE.md structure, formatting, and quality. Use when checking context files for compliance, ensuring proper structure, or verifying before commits.