Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From claude-code-expert
Diagnoses and fixes Claude Code setup and runtime issues via full diagnostics or targeted checks (auth, MCP, hooks, config, etc.), producing PASS/WARN/FAIL reports with recommended and auto-fixes.
How this command is triggered — by the user, by Claude, or both
Slash command
/claude-code-expert:cc-troubleshootThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /cc-troubleshoot — Claude Code Issue Diagnostics Diagnose and fix Claude Code setup and runtime issues. ## Usage ## Issue Types ## Implementation When invoked, activate the `claude-code-debugger` agent to run systematic diagnostics: ### Full Diagnostics (no issue-type) 1. Environment check (Node, npm, Claude Code version) 2. Authentication check (API key, provider) 3. Configuration validation (settings.json, .mcp.json, CLAUDE.md) 4. MCP server status 5. Hook validation 6. Plugin validation 7. Check lessons-learned for known issues 8. Report all findings with severity ### Targete...
Diagnose and fix Claude Code setup and runtime issues.
/cc-troubleshoot [issue-type]
/cc-troubleshoot # Run full diagnostics
/cc-troubleshoot auth # Authentication issues
/cc-troubleshoot mcp # MCP server issues
/cc-troubleshoot hooks # Hook issues
/cc-troubleshoot config # Configuration issues
/cc-troubleshoot permissions # Permission issues
/cc-troubleshoot performance # Performance issues
/cc-troubleshoot install # Installation issues
/cc-troubleshoot plugins # Plugin issues
When invoked, activate the claude-code-debugger agent to run systematic diagnostics:
Focus only on the specified area with deeper analysis.
=== Claude Code Diagnostics ===
[PASS] Node.js v20.11.0
[PASS] Claude Code v1.2.3
[PASS] API Key configured (54 chars)
[PASS] settings.json valid
[WARN] 3 unresolved issues in lessons-learned.md
[FAIL] MCP server "postgres" not responding
[FAIL] Hook script .claude/hooks/guard.sh not executable
=== Recommended Fixes ===
1. Fix MCP server: Check DATABASE_URL env var
2. Fix hook: chmod +x .claude/hooks/guard.sh
When possible, offer to automatically fix issues:
npx claudepluginhub markus41/claude --plugin claude-code-expert/diagnoseRuns a full health check on cc-suite setup, diagnoses issues, and offers auto-fixes for missing or misconfigured artifacts.
/statusline-doctorDiagnoses claude-2x-statusline installation, config, and runtime issues via Bash doctor script, optionally fixing them interactively. Supports --fix, --report, --json, --explain [segment] flags.
/doctorRuns a comprehensive diagnostic on pro-workflow setup, hooks, context usage, MCP servers, CLAUDE.md size, git status, and settings to identify configuration issues.
/statusInspects Codex CLI installation, runs doctor diagnostics, checks configuration and API key, lists MCP server registrations, and reports overall readiness.
/doctorPerforms preflight diagnostic on claudex: verifies bash, codex CLI, state directory, plugin file integrity, and hook fail-open. Exit 0 if pass, 1 if fail.
/omc-doctorExecutes the omc-doctor diagnostics from the OMC plugin, checking compatibility and health of the Claude Code environment.