← ClaudeAtlas

clean-mvplisted

Whole-codebase cruft-removal sweep — find and DELETE dead code, unused symbols and files, legacy/back-compat shims, YAGNI abstractions, stale TODOs, and commented-out code. Every deletion is backed by a Proof-of-Deadness evidence checklist and gated by batched user confirmation, then verified via format + test. TRIGGER when: the user wants to "clean up the codebase", "remove dead code", "delete unused stuff", "strip legacy shims", a post-refactor lean-down, or a periodic MVP-discipline sweep. DO NOT TRIGGER when: the user wants to clean up the current diff or specific changed files (use /refactor — it improves code, this sweeps it away), rank architecture-level rot and ball-of-mud hotspots (use /arch-health — proposes only), or hunt correctness/security bugs (use /code-review).
mik2win/foureyes · ★ 2 · Code & Development · score 79
Install: claude install-skill mik2win/foureyes
# Clean MVP: $ARGUMENTS MVP-stage discipline: if code is not reachable from a live entry point, delete it. No back-compat shims, no deprecated aliases, no "just in case" abstractions — anything needed later can be recovered from git history. This skill SWEEPS and APPLIES deletions; it does not redesign what stays (`/refactor`) and does not judge architecture (`/arch-health`). `$ARGUMENTS` optionally scopes the sweep to a file, directory, or module; empty = the whole source tree per `PROJECT.md` → Architecture. --- ## Phase 0 — Load profile 1. Read `.claude/PROJECT.md` — **Commands** (`test`, `lint`, `format`), **Architecture** (source layout, layers, entry points), and **Conventions notes**. If missing or still `TEMPLATE`, fall back to the root `CLAUDE.md` (always in context) when it carries the commands/architecture — note you're running without a kit profile; only if *neither* has them, **STOP** and tell the user to run `/bootstrap` first. 2. Read the installed rules in `.claude/rules/*` whose `paths` match the sweep scope — they define the stack's idioms (module-export conventions, DI/registry patterns, intentional extension points). Use them; never assume a stack. 3. If `CONTEXT.md` exists, read it so findings are named in the project's vocabulary. --- ## Phase 1 — Sweep categories Scan the scope for each category. Grep-driven; read a file in full before judging its symbols. 1. **Unused imports/symbols** — run the `lint` command from PROJECT.md