repo-cleanup

NickCrew 的头像作者 NickCrew

在需要清理死代码、构建工件、未使用的依赖项、过时的文档或陈旧的测试时使用 - 提供安全的清理工作流程、验证步骤和代码、依赖项、文档、测试和冲刺存档的报告模板。

📖 中文导读:在需要清理死代码、构建工件、未使用的依赖项、过时的文档或陈旧的测试时使用 - 提供安全的清理工作流程、验证步骤和代码、依赖项、文档、测试和冲刺存档的报告模板。 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。

name: repo-cleanup description: 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.

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