Treat
Context cleaning for Claude Code — prune bloated sessions, protect Agent Teams from context loss, auto-guard with tiered pruning
npx -y skills add Ruya-AI/cozempic --skill treatAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Prune bloated session with a prescription. Removes progress ticks, stale reads, duplicate content, and more.
SKILL.md
2.1 KB, as published. Nobody here has run it
Apply a pruning prescription to the current session. Default is standard if no argument given.
When to use treat vs reload: prefer the reload skill — it does the same prune plus auto-resume in one step (/exit → new terminal opens with the pruned session). Use treat only when the user explicitly wants to stay in the current session, work in a multi-pane setup, or resume manually.
Steps
-
Diagnose first — show the user what they're working with:
cozempic current --diagnose -
Dry-run the treatment — show savings without applying:
cozempic treat current -rx $ARGUMENTSIf no argument was provided, use
standard:cozempic treat current -rx standard -
Show results — present the dry-run output including token savings (the
Tokens:line). Always surface both byte and token savings. -
Ask confirmation — use AskUserQuestion to confirm before applying.
-
Apply on confirmation:
cozempic treat current -rx $ARGUMENTS --execute -
Tell the user: "Treatment applied. A backup was created automatically. To resume with the pruned session, exit and run
claude --resume. (Tip: next time, thereloadskill does this in one step —/exitand a fresh terminal opens automatically.)"
Prescriptions
| Rx | Strategies | Typical Savings |
|---|---|---|
gentle | progress-collapse, file-history-dedup, metadata-strip | 40-55% |
standard | gentle + thinking-blocks, tool-output-trim, stale-reads, system-reminder-dedup | 50-70% |
aggressive | standard + error-retry-collapse, document-dedup, mega-block-trim, envelope-strip | 70-95% |
Safety
- Always dry-run first — never execute without showing the user what will change
- Backups are automatic (timestamped .bak files)
- Never touches uuid/parentUuid — conversation DAG stays intact