← ClaudeAtlas

cleanlisted

Repository Cleanup Command
sequant-io/sequant · ★ 1 · Code & Development · score 72
Install: claude install-skill sequant-io/sequant
<!-- sequant:local-override --> > **Local overrides (read this first).** Before following any instruction below, check whether `.claude/.local/skills/clean/overrides.md` exists. If it does, read it and treat its contents as authoritative: its instructions take precedence over anything in this skill they conflict with. This is the supported way to tailor `/clean` without forking it — `overrides.md` lives under `.claude/.local/`, which `sequant update` and `sync` never overwrite. # Repository Cleanup Command Comprehensive, safe repository cleanup that archives stale files, removes artifacts, and commits changes. ## Safety First Before making ANY changes: 1. Verify we're on `main` branch with clean working tree 2. Run `npm run build` to ensure current state builds 3. Create a safety checkpoint (stash any uncommitted work) ## Cleanup Categories ### Category 1: Safe to Auto-Archive (No Review Needed) These files are always safe to archive - they're historical artifacts: **Root directory patterns:** - `*.backup` files (e.g., `CLAUDE.md.backup`) - `CODE_REVIEW_PR_*.md` - Old PR reviews - `*_AUDIT.md` files older than 30 days - One-off shell scripts with dates in names **docs/ patterns:** - `ISSUE_*_PHASE_*.md` - Issue implementation specs (work is done) - `*_IMPLEMENTATION.md` older than 30 days - `content-audit-*.md` - Point-in-time audits - City-specific audit files (e.g., `NYC_*_AUDIT.md`, `LA_*_REPORT.md`) ### Category 2: Review Before Archiving These need a quick che