mcpField
R
repo-cleanup

repo-cleanup

github.com/nickcrewDevelopment62174 installsUpdated 17w ago
Repository

About repo-cleanup

A skill for safely cleaning up code repositories across code, dependencies, documentation, tests, and sprint artifacts. Its repeatable workflow emphasizes checking usage, keeping rollback options, and validating changes.

Key features

  1. 01Scope and safety-mode definition
  2. 02Baseline and rollback checkpoints
  3. 03Usage checks before removal
  4. 04Test and build validation
  5. 05Sprint artifact archiving

Use cases

  1. 01Removing generated files and caches
  2. 02Checking suspected dead code or dependencies
  3. 03Updating outdated documentation
  4. 04Organizing sprint closure artifacts

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nickcrew/claude-cortex --skill repo-cleanup

After installing, type/repo-cleanupin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
archive-sprint.md
code-cleanup.md
deps-cleanup.md
docs-cleanup.md
test-cleanup.md

Details

From the project README

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

TaskLoad reference
Code cleanupskills/repo-cleanup/references/code-cleanup.md
Dependency cleanupskills/repo-cleanup/references/deps-cleanup.md
Docs cleanupskills/repo-cleanup/references/docs-cleanup.md
Test cleanupskills/repo-cleanup/references/test-cleanup.md
Sprint archiveskills/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

Comments

Markdown supported