repo-cleanup

Use when a repository needs cleanup of dead code, build artifacts, unused dependencies, outdated docs, or stale tests - provides safe cleanup workflows, validation steps, and reporting templates for code, deps, docs, tests, and sprint archives.

⭐4stars🔀2forks📁View on GitHub🕐Updated Dec 31, 2025

When & Why to Use This Skill

The Repo Cleanup skill is a comprehensive utility designed to streamline repository maintenance and reduce technical debt. It provides automated, safe workflows for identifying and removing dead code, unused dependencies, outdated documentation, and stale test files. By incorporating validation steps and reporting templates, it ensures a lean and high-performance codebase while minimizing the risk of breaking changes during cleanup operations.

Use Cases

  • Technical Debt Reduction: Safely identify and remove unreachable code, unused variables, and obsolete files to improve code readability and long-term maintainability.
  • Dependency Pruning: Detect and eliminate unused third-party packages and libraries to reduce build times, minimize security vulnerabilities, and shrink the project footprint.
  • CI/CD Optimization: Clean up legacy build artifacts, caches, and redundant test files to optimize storage usage and accelerate continuous integration pipelines.
  • Documentation & Test Alignment: Audit the repository to remove or update outdated documentation and brittle tests that no longer reflect the current system behavior.
  • Structured Sprint Archiving: Automate the archiving of sprint-specific artifacts and temporary files during project handovers or sprint closures to maintain an organized workspace.
namerepo-cleanup
descriptionUse when a repository needs cleanup of dead code, build artifacts, unused dependencies, outdated docs, or stale tests - provides safe cleanup workflows, validation steps, and reporting templates for code, deps, docs, tests, and sprint archives.

Repo Cleanup

Overview

Establish a safe, repeatable cleanup workflow for code, dependencies, docs, tests, and sprint artifacts. Minimize risk by validating usage, archiving before deletion, and verifying with tests.

When to Use

  • Repository bloat (generated artifacts, caches, unused files)
  • Dead code or unused dependencies suspected
  • Docs drifted from actual behavior
  • Tests are brittle, redundant, or mislocated
  • Sprint closure needs structured archiving

Avoid when:

  • Active incident response is ongoing
  • The target area lacks owners or rollback coverage

Quick Reference

Task Load reference
Code cleanup skills/repo-cleanup/references/code-cleanup.md
Dependency cleanup skills/repo-cleanup/references/deps-cleanup.md
Docs cleanup skills/repo-cleanup/references/docs-cleanup.md
Test cleanup skills/repo-cleanup/references/test-cleanup.md
Sprint archive skills/repo-cleanup/references/archive-sprint.md

Workflow

  1. Define scope and safety mode (safe vs aggressive).
  2. Capture baseline state (git status, key tests, backups).
  3. Load the relevant reference file(s) for the target area.
  4. Execute cleanup steps with usage checks before removal.
  5. Validate changes (tests, build, lint, or doc checks).
  6. Report outcomes (actions taken, risks, follow-ups).

Output

  • Summary of actions and files touched
  • Validation results and remaining risks
  • Follow-up recommendations or backlog items

Common Mistakes

  • Deleting without confirming usage or regenerability
  • Skipping baseline tests and rollback checkpoints
  • Removing dependencies without updating build/test scripts
  • Collapsing docs without preserving entry points