What problem does it solve?
This Skill tackles the challenge of maintaining a clean and optimized code repository by systematically identifying and addressing stale, duplicate, or unnecessary files and structural issues.
Core Features & Use Cases
- File Inventory & Classification: Maps all tracked files, categorizing them by liveness (active, dormant, dead, duplicate).
- Value Assessment: Employs a four-question framework to determine if files should be kept, merged, activated, or archived before deletion.
- Content Consolidation: Merges overlapping content from multiple files into a single, crisp document.
- Structural Audits: Identifies repo-level issues like stale configurations, orphaned tests, and documentation rot.
- Adaptive Strategy: Pivots cleanup strategy based on discovered value, prioritizing preservation and optimization over simple deletion.
- Use Case: A large project has accumulated many old scripts and documentation files over time. This Skill can be used to identify which files are truly unused, which can be reactivated, and which contain unique value that should be preserved or consolidated, leading to a smaller, more manageable repository.
Quick Start
Use the repo-maintenance skill to perform an adaptive cleanup of the current repository, focusing on reducing file count.