Menu
Health check for the context-optimizer plugin install — verifies versions, hooks, data dir, model config, and reports any issues
| name | cco-doctor |
| description | Health check for the context-optimizer plugin install — verifies versions, hooks, data dir, model config, and reports any issues |
| license | MIT |
| allowed-tools | ["Bash","Read"] |
When the user runs /cco-doctor or reports the plugin "isn't working", run a quick health check.
Standard run (fast — under 1s):
node ${CLAUDE_PLUGIN_ROOT}/src/doctor.js
With test suite (slower — runs all unit tests):
node ${CLAUDE_PLUGIN_ROOT}/src/doctor.js --tests
package.json existplugin.json and package.json)hooks.json is valid JSON with all expected event typessrc/~/.claude-context-optimizer/ is writablepatterns.json size is reasonableTranslate the doctor output into plain language. If anything is fail, walk the user through the fix:
npm run sync-version/cco-clean/cco-budget set <smaller> or pick a 1M-context modelIf everything is pass, confirm "плагин в порядке, текущая версия Х.Y.Z" and stop.
Configure token budget limits, auto-compact settings, and view current budget status (model-aware — supports Opus 4.7 1M context tier)
Analyze the user's last prompt for clarity, scope and specificity — give a quality score and concrete suggestions to make the next prompt produce better results
Build an optimal context pack for the user's task — ranked file list with offset/limit suggestions, based on git state, mentioned paths, and historical patterns
Calculate monthly token savings and ROI by model
Show recent session summaries for quick context recovery
Show ContextShield status and waste protection stats