tidy — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited tidy (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
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 domain skill. Domain procedures live in those domain skills — this skill owns only scope detection, dispatch, and the output contract. Tidy's deletions are compress-class (behavior-preserving: dead/redundant/structural); a request to remove a live capability is purge — route it out to refactor-break-bw-compat, never tidy inline.
Invariants:
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) |
| "remove/drop/kill a live capability", compat-shim or feature-flag teardown named | Purge | refactor-break-bw-compat skill |
| No clear signal | — | Ask: "What are we tidying — code, memory, workspace, git, docs, or ICM?" |
Purge is a behavior change, not a tidy — detect purge-intent and dispatch out; never perform capability removal inline (violates the behavior-commit-separation invariant).
These three domains are handled inline without a dedicated domain skill.
fd -t f -E '.git' -E 'target' -E '_build' \
'(\.(tmp|bak|outline)|repomix-output)' .
fd -t f /tmp -g '<session-prefix>-*' 2>/dev/nullrip (not rm). Report count and paths.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.<!-- VERIFY --> and surface to the user rather than deleting.Run icm list --sort recent | head -30; for each stale entry show the current content plus the proposed replacement before calling icm update. For decisions made in this session not yet captured, show the proposed icm store call before executing. Write only on explicit user confirmation per entry.
After completing each domain, emit exactly:
Tidy — <domain>
Removed: N (up to 5 paths/names; "…and M more" if larger)
Fixed: N
Proposed: N (awaiting confirmation)
Skipped: N (<one-phrase reason>)
Next: <one sentence, e.g. "Run build to verify" or "Nothing else in scope">If nothing needed tidying: Tidy — <domain>: nothing to do.
git move --fixup when embedding alongside active work.~/.claude/claude/system-prompt-baseline.md, the baseline wins.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.