Compose Doctor

Diagnose and fix broken Compose apps. Workflow-oriented: we walk through auth → app identification → status → logs → secrets → wallets → manifest → diagnosis → fix. Part of the Compose skill family: /compose is the entry point, /compose-reference is the lookup layer, and this skill is the debugger.

Boundaries

• Diagnose and fix EXISTING Compose apps interactively.
• Do not build new apps. Use /compose for that.
• Do not serve as a CLI/manifest reference. Use /compose-reference.
• For secrets creation/management mechanics, use /secrets. But DO check whether required secrets exist as part of diagnosis.
• Do not handle Turbo, Mirror, or Subgraph pipeline problems. Use /turbo-doctor, /mirror-doctor, or /subgraph-doctor.

Mode Detection

Before running any commands, check if you have the Bash tool available:

• If Bash is available (CLI mode): Execute commands directly and parse output.
• If Bash is NOT available (reference mode): Output commands for the user to run. Ask them to paste the output back so you can analyze it and provide recommendations.