| name | doctor |
| description | Diagnose the Oh My Antigravity installation and Antigravity CLI plugin lifecycle. |
Doctor
When invoked, diagnose the current Oh My Antigravity installation immediately.
Use this skill when the user asks whether Oh My Antigravity is installed,
whether Antigravity CLI can discover the plugin, or why a workflow command is
not available.
Execution Contract
-
Run omagy doctor --json from the current workspace.
-
If omagy is not on PATH, and the checkout contains
dist/packages/cli/src/omagy.js, run:
node dist/packages/cli/src/omagy.js doctor --json
-
Do not inspect the repository before running the diagnostic command unless
both commands above are unavailable.
-
Do not run install, link, or build commands. In particular, do not run
npm link, npm install, npm install -g, npm run build,
omagy setup, or agy plugin install.
-
Report failing checks first, then warnings, then the pass count. Include the
command that was run and whether it exited successfully.
-
Treat hook launcher or Stop hook smoke failures as runtime failures, not
cosmetic plugin metadata issues. They usually mean omagy setup has not
written hooks/omagy-command.json or the installed hook shim cannot reach
the built CLI.
-
Treat Workflow command failures as lifecycle-runtime failures. They mean
omagy workflow status|next|cancel|complete is not available, so Ralph and
Ultrawork cannot be reliably completed through the supported surface.