← ClaudeAtlas

mdsweeplisted

Audit and clean up stale agent-generated markdown artifacts (SUMMARY.md, PLAN.md, HANDOFF.md, scratch notes) in a repository. Use when a repo is cluttered with old agent output, when stale plans or reports risk being read as current context, before a repo handoff, or when the user asks to clean up markdown sprawl.
szp2005/mdsweep · ★ 0 · Data & Documents · score 72
Install: claude install-skill szp2005/mdsweep
# mdsweep mdsweep finds markdown artifacts left behind by agent sessions, grades them (`active` / `stale` / `orphan`), and can move orphans into a reversible quarantine. It never deletes files. ## When to run it - The repo root or subdirectories contain accumulating `SUMMARY.md`, `PLAN_*.md`, `*_REPORT.md`, `HANDOFF*.md`, draft or scratch files. - You are about to rely on an existing plan/summary file and want to know whether it is current or abandoned. - The user asks to tidy the repo, reduce context noise, or prepare a handoff. ## Steps 1. **Scan first, always.** Read-only: ```sh mdsweep scan [path] --json ``` If mdsweep is not installed: `npx mdsweep scan [path] --json`. 2. **Interpret the grades.** - `active` — touched in the last 14 days (`--days` to adjust). Leave alone. - `stale` — old but still referenced by other files (`refs` > 0). Do not quarantine; if a reference in CLAUDE.md/README points at an abandoned plan, propose updating the referencing file instead. - `orphan` — old, zero inbound references. These are the only quarantine candidates. - `signals` explains why each file was flagged (filename pattern, Claude co-authored commit, untracked, generated frontmatter). Mention this when summarizing. 3. **Before quarantining, show the user the exact list.** Present every orphan (path, size, age) and get explicit confirmation. Never run `--apply` without the user approving the specific file list in thi