agentsclimarketplace
Sign in

Repo cleanup

Skill NickCrew/Claude-Cortex/skills/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.From its SKILL.md

Install
npx -y skills add NickCrew/Claude-Cortex --skill repo-cleanup

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 23 stars23 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.2 KB, 374 tokens by cl100k_base, as published. Nobody here has run it

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

What ships with it: 5 files

51.0 KB alongside SKILL.md

references/

Keep looking

Skills are one crate of 326,851. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.