tidy

Tidy — structural-cleanup dispatcher

Compress first. Before adding complexity, reduce coupling. Before changing behavior, improve structure. This skill detects what needs tidying from context and routes to the right sibling skill. Domain procedures live in the siblings — this skill owns only scope detection, dispatch, and the output contract.

Invariants:

• Every tidy action is atomic and scoped to what is already in view.
• Tidy commits are always separate from behavior commits.
• No opportunistic sweeps beyond the declared or clearly active scope.

---

Scope detection

Inspect context in priority order and dispatch to the first matching domain:

Signal	Domain	Dispatch to
File path(s), active diff, or cargo/dune target named	Code	cleanup-codebase skill
memory/ directory, MEMORY.md, or memory file(s) named	Memory	memory-clean then memory-update skills
.outline/, /tmp scratch, *.tmp, *.bak, repomix packs	Workspace	Inline (see below)
git sl, commit stack, commit message(s) named	Git	git-branchless skill + atomic-commit skill
Docs, comments, ADRs, READMEs, plan files named	Docs	Inline (see below)
User explicitly says "tidy ICM" or names an ICM topic	ICM state	Inline (see below)
No clear signal	—	Ask: "What are we tidying — code, memory, workspace, git, docs, or ICM?"

---

Inline procedures (workspace, docs, and ICM state)

These three domains are handled inline without a dedicated sibling skill.

Workspace

1. Discover scratch artifacts in scope:

   fd -t f -E '.git' -E 'target' -E '_build' \
     '(\.(tmp|bak|outline)|repomix-output)' .
   fd -t f /tmp -g '<session-prefix>-*' 2>/dev/null
   

2. Confirm each is truly scratch (not referenced by any open plan, task, or active diff).
3. Remove with rip (not rm). Report count and paths.

Docs

1. Scan in-scope file(s) for: stale TODO/FIXME (git-blame date > 6 months), comments contradicting current code, commented-out code blocks, multi-paragraph docstrings on non-API-surface functions, overclaims about external contracts.
2. Show the current text + proposed change for each candidate. Edit only on confirmation or for purely cosmetic fixes (whitespace, spelling).
3. Overclaims: annotate with <!-- VERIFY --> and surface to the user rather than deleting.