From ctx
Troubleshoots ctx system with structural health checks, event log analysis, and config reviews; suggests actions for hook failures, stale context, and anomalies.
npx claudepluginhub activememory/ctx --plugin ctxThis skill is limited to using the following tools:
Diagnose ctx problems by combining structural health checks with
Runs context-mode diagnostics checking runtimes, hooks, FTS5, plugin registration, npm and marketplace versions. Invoke via /context-mode:ctx-doctor.
Audits Elle context system at ~/.claude/.context/core/ for staleness, contradictions, bloat, missing data, sync issues, and improvements. Use when responses feel generic, outdated, or after changes.
Runs diagnostics on Claude Octopus plugin environment across 11 categories: providers, auth, config, hooks, scheduler, state, skills, and more. Use for setup verification and issue detection.
Share bugs, ideas, or general feedback.
Diagnose ctx problems by combining structural health checks with event log analysis.
/ctx-status)/ctx-drift)ctx system message)/ctx-pause)Follow this triage sequence:
Run ctx doctor --json to get the full structural health report.
ctx doctor --json
Parse the JSON output. Note any warnings or errors.
If the doctor report shows event logging is enabled, query recent events:
ctx system events --json --last 100
If the user is asking about a specific hook:
ctx system events --hook <hook-name> --json --last 20
If event logging is not enabled, note: "Enable event_log: true in
.ctxrc for hook-level diagnostics."
Based on findings, check additional sources:
.claude/settings.local.json to verify hook registrationctx system message list to check for silenced hooks.ctxrc to check configurationctx remind list for pending remindersStructure your report as:
## Doctor Report
### Structural health
- Summarize ctx doctor results
### Event analysis (if available)
- Patterns, gaps, or anomalies in event data
- Specific hook behavior observations
### Suggested actions
- [ ] Actionable items based on findings
Present actionable next steps but do NOT auto-fix anything. The user decides what to act on.
| Source | Command | What it reveals |
|---|---|---|
| Structural health | ctx doctor --json | All mechanical checks |
| Event log | ctx system events --json --last 100 | Recent hook activity |
| Event log (filtered) | ctx system events --hook <name> --json | Specific hook |
| Reminders | ctx remind list | Pending reminders |
| Hook messages | ctx system message list | Custom vs default |
| RC config | Read .ctxrc | Configuration |
If event logging is not enabled, the skill still works with reduced
capability. Run ctx doctor for structural checks and note that
event-level diagnostics require event_log: true in .ctxrc.