v1.0.0 · 2026-10-16
First release: reads a snapshot of a Claude Code session (context size measured or guessed, the task and where it stands, git status, background processes, the plan or notes file, what the person asked) and gives one line per problem with a fixed code, the reason and a step, then one decision line: /clear, /compact with a focus text, finish first, or keep going. Before a fresh session it checks six blockers: results only in the chat, no next step in the plan, uncommitted or unpushed work, changes by another session, background processes and temporary deployments, a secret about to be written into notes. Timing: a deploy or migration in progress, waiting for auto-compact, a size judged by feel, a cold cache after a long break, the same correction made more than twice. Command choice: /compact on finished work, a bare /compact, an agent that claims it will clear the session itself. While working: huge files and logs read whole. The agent never types the command; it saves, then tells the person the one line. Facts: the official Claude Code pages (version 2.1.301) read on 16 October 2026 and our own measurements of 10 September and 16 October 2026; the skill tells the reader that the current pages win.
Test record (30 snapshots, one run per model and case, Claude Code 2.1.301): - First run (120 runs) read failure by failure; then the skill text was changed in two places (SIZE-GUESSED is reported with the measured number even when the decision is keep going; finish first only for a step in progress or the last one or two steps of the task, while saving before a fresh session is a finding and the decision stays /clear), the shared request gained rule (4) (the environment the model runs in is not the session in the snapshot), and both sides were run again in full. - Second run, read failure by failure. No-skill checks widened for both sides, each with the real phrase in control.mjs and a mutation that turns it red: an arbitrary moment for auto-compact said in the next sentence; a next step that exists only in the conversation, or a Next entry written as "Next:"; a TBD that leaves steps "aren't written"; three hours idle meaning re-reading the full context; four corrections that repeat the same mistake in the same context; "no reason to clear or compact now" counts as keep going; "a clear now would save little" is a noun, not advice to clear. - clean-finish-first: the owner's rule in the shared request names the first clean point after 150 000 tokens, and the snapshot says the point is clean, so /clear now is scored right next to finish first, on both sides; keep going and /compact still fail. - mid-operation-b reworded: "migration ran, release not started, the person has to leave" allowed a fresh session at a stable state (an added column nothing reads yet). Now the migration reported success two minutes ago and nobody has checked it; run again on both sides with both models (4 runs). - Kept as failures: Sonnet without the skill stayed in a 60 000-token session for an unrelated next task, and committed two files another session had changed; Haiku without the skill cleared before the live check of a deploy, missed an uncommitted file, and took a writable place from its own environment on two read-only folders; Haiku with the skill reported uncommitted work for a plan line not yet written while the tree was clean. - Measured: Sonnet 30/30 with the skill, 28/30 without; Haiku 29/30 with, 26/30 without. Runs: 120 + 120 + 4. - Price: 30000 micro-USDC ($0.03), by the Sonnet gain of 2.