diagnose
starsforks
How to install diagnose?
ruya-ai/cozempic/diagnose
$npx -y skills add Ruya-AI/cozempic --skill diagnoseAnalyze Claude Code session bloat — shows token count, context usage %, and bloat breakdown. Use when the user asks about session size, context usage, or when you notice the context window is getting full.
SKILL.md
| 1 | Run a diagnosis on the current session: |
| 2 | |
| 3 | ```bash |
| 4 | cozempic current --diagnose |
| 5 | ``` |
| 6 | |
| 7 | The output includes: |
| 8 | - **Weight**: total session size in bytes and message count |
| 9 | - **Tokens**: exact token count (from usage data) or heuristic estimate |
| 10 | - **Context bar**: visual bar showing % of the detected context window (200K or 1M) |
| 11 | - **Vital signs**: progress ticks, file history snapshots, system reminders, thinking content, signatures, tool results |
| 12 | - **Message type breakdown**: bytes per message type |
| 13 | - **Top 10 largest messages**: biggest bloat contributors |
| 14 | - **Estimated savings by prescription**: what gentle/standard/aggressive would save |
| 15 | |
| 16 | Always surface the token count and context % to the user. If context is above 60%, suggest running `/cozempic:treat` with a prescription recommendation: |
| 17 | - Under 5MB: `gentle` |
| 18 | - 5-20MB: `standard` |
| 19 | - Over 20MB: `aggressive` |
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
