/omg-doctor

/omg-doctor

Health-check the oh-my-god install. Verifies every file the plugin needs and tells you exactly which step is missing.

When to use

• First-run sanity check after /plugin install
• Hooks aren't firing
• Errors mentioning "Cannot find module" or "schema.sql not found"
• After upgrading the plugin via /plugin update
• Anytime /omg-status shows weird state and you want to know why

Checks performed

1. Plugin root has package.json, hooks/hooks.json, roles.json
2. Build output exists: dist/core/store.js, dist/core/schema.sql, dist/roles.json, harvest, gate, heuristic, roles loader
3. node_modules/better-sqlite3 is installed (native binding)
4. All three hook scripts are present
5. ~/.omg/state.db exists
6. SQLite schema has all 5 tables (sessions, claims, AC, evidence, gates)
7. roles.json parses cleanly and lists at least one role

What to do when invoked

1. Run the doctor script via Bash:

   node "$CLAUDE_PLUGIN_ROOT"/scripts/omg-doctor.mjs
   

2. Read the output. Each line is ✅ check name (info) or ❌ check name (info).

3. If everything passes, tell the user "oh-my-god is healthy."

4. If anything fails, the script's last line will list suggestions:

   • dist/ missing → cd <plugin root> && npm run build
   • node_modules missing → cd <plugin root> && npm install
   • DB missing → /omg-setup
   • roles.json invalid → check syntax + re-run

   Surface those hints to the user verbatim.

Expected output (healthy)

✅ plugin root has package.json (/Users/<you>/.claude/plugins/cache/...)
✅ hooks/hooks.json present
✅ roles.json present
✅ dist/core/store.js (built)
... (more checks)
✅ DB schema has all 5 tables (acceptance_criteria, claims, evidence, gates, sessions)
✅ roles.json parses cleanly (5 roles: default, executor, explorer, architect, reviewer)

[omg-doctor] 17 passed, 0 failed

Exit codes

• 0 — all checks passed
• 1 — at least one check failed