skill-prune

To prune orphan files, run a cleanup pass that detects content unreferenced by any SKILL.md or reference file for 60 days. It generates a detailed deletion plan you review before removals are applied.

The best way to deduplicate outdated reference files is to consolidate duplicates and superseded scenarios during a prune pass. This prevents confusion and maintenance overhead while preserving KEEP annotations for required content.

Automate quarterly maintenance by running a prune pass to guide cleanup operations. It maintains a deletion plan, logs decisions for traceability, and preserves KEEP annotations to ensure safety across skill and reference files.

Yes, you can review content before deletion during a linter cleanup. The prune process generates a deletion plan and logs decisions to ensure traceability and safety, requiring you to review before applying any removals.

The pruning process preserves critical reference hygiene by explicitly maintaining KEEP annotations during the cleanup. It logs all deletion decisions to ensure traceability and safety across your skill and reference files.

You should avoid automated deduplication when you cannot review the deletion plan beforehand. Pruning relies on user review before applying removals, ensuring that orphan files and superseded scenarios are safely consolidated without data loss.