treat
starsforks
How to install treat?
ruya-ai/cozempic/treat
$npx -y skills add Ruya-AI/cozempic --skill treatPrune bloated session with a prescription. Removes progress ticks, stale reads, duplicate content, and more.
SKILL.md
| 1 | Apply a pruning prescription to the current session. Default is `standard` if no argument given. |
| 2 | |
| 3 | **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. |
| 4 | |
| 5 | ## Steps |
| 6 | |
| 7 | 1. **Diagnose first** — show the user what they're working with: |
| 8 | ```bash |
| 9 | cozempic current --diagnose |
| 10 | ``` |
| 11 | |
| 12 | 2. **Dry-run the treatment** — show savings without applying: |
| 13 | ```bash |
| 14 | cozempic treat current -rx $ARGUMENTS |
| 15 | ``` |
| 16 | If no argument was provided, use `standard`: |
| 17 | ```bash |
| 18 | cozempic treat current -rx standard |
| 19 | ``` |
| 20 | |
| 21 | 3. **Show results** — present the dry-run output including token savings (the `Tokens:` line). Always surface both byte and token savings. |
| 22 | |
| 23 | 4. **Ask confirmation** — use AskUserQuestion to confirm before applying. |
| 24 | |
| 25 | 5. **Apply on confirmation**: |
| 26 | ```bash |
| 27 | cozempic treat current -rx $ARGUMENTS --execute |
| 28 | ``` |
| 29 | |
| 30 | 6. **Tell the user**: "Treatment applied. A backup was created automatically. To resume with the pruned session, exit and run `claude --resume`. (Tip: next time, the `reload` skill does this in one step — `/exit` and a fresh terminal opens automatically.)" |
| 31 | |
| 32 | ## Prescriptions |
| 33 | |
| 34 | | Rx | Strategies | Typical Savings | |
| 35 | |----|-----------|----------------| |
| 36 | | `gentle` | progress-collapse, file-history-dedup, metadata-strip | 40-55% | |
| 37 | | `standard` | gentle + thinking-blocks, tool-output-trim, stale-reads, system-reminder-dedup | 50-70% | |
| 38 | | `aggressive` | standard + error-retry-collapse, document-dedup, mega-block-trim, envelope-strip | 70-95% | |
| 39 | |
| 40 | ## Safety |
| 41 | - Always dry-run first — never execute without showing the user what will change |
| 42 | - Backups are automatic (timestamped .bak files) |
| 43 | - Never touches uuid/parentUuid — conversation DAG stays intact |
People who liked this also viewed
6 picksType
- azure-diagnosticsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deploySkillsJul 2026
- systematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesSkillsJul 2026
- safe-debugRigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training SkillsMay 2026
- explore-runRigor Improve / Rigor Explore run leaf skill for bounded exploratory evidence in deep learning research repositories. Use when the researcher explicitly authorizes exploratory runs such as small-subseSkillsMay 2026
- minimal-run-and-auditRigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation SkillsMay 2026
- insforge-debugUse when diagnosing problems in an InsForge project — reactive failures (SDK error object, HTTP 4xx/5xx, gateway timeout 502/503/504, edge function failure or timeout, login/OAuth/auth errors, RLS denSkillsJul 2026
