skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
nickcrew/claude-cortex165 installs

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.

How do I install this agent skill?

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

Is this agent skill safe to install?

  • Gen Agent Trust Hubwarn

    The repo-cleanup skill automates repository maintenance tasks such as archiving artifacts, deleting branches, and cleaning up dependencies. It uses standard developer tools including shell commands for file management and npm-based analysis utilities. Users should review the proposed deletions, especially when dealing with environment files or remote branches.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

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

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/nickcrew/claude-cortex/repo-cleanup">View repo-cleanup on skillZs</a>