ワンクリックで
babysitter-doctor
Diagnose babysitter run health — journal integrity, state cache, effects, locks, sessions, logs, and disk usage.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Diagnose babysitter run health — journal integrity, state cache, effects, locks, sessions, logs, and disk usage.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Orchestrate complex, multi-step AI workflows with quality convergence loops, event-sourced state, and human-in-the-loop approval gates. Use when the user wants to babysit a task, orchestrate a workflow, run quality-gated development, resume a previous orchestration run, diagnose run health, plan without executing, set up a project or user profile for babysitter, or assimilate an external methodology. Also use when the user mentions "babysitter", "orchestrate", "babysit", "quality loop", or "convergence loop".
Help and documentation for babysitter commands, processes, skills, agents, and methodologies.
Plan a babysitter workflow without executing it. Focus on creating the best process possible.
Install or refresh a team-pinned babysitter runtime/content setup from lockfile.
Start a babysitter orchestration run. Use this command to start babysitting a complex workflow.
Analyze a completed or in-flight run and propose process improvements for future runs.
| name | babysitter:doctor |
| description | Diagnose babysitter run health — journal integrity, state cache, effects, locks, sessions, logs, and disk usage. |
| argument-hint | [run-id] Optional run ID to diagnose. If omitted, uses the most recent run. |
Comprehensive diagnostic agent for babysitter runtime health. Performs 10 mandatory health checks on a specific run (or the most recent run if no ID is provided).
If no run-id argument provided, find the most recent run:
ls -t .a5c/runs/ | head -1
For each check, report PASS, WARN, or FAIL.
.a5c/runs/<runId>/.a5c/runs/<runId>/journal.jsonl existsstate.json against journal eventsrun.lock file.a5c/logs/ for hook logs.a5c/runs/<runId>/ total sizenode --check@a5c-ai/babysitter-sdk dependency is installedsh -n passes for shell scriptsnode --check passes for JS hooksPrint a summary table:
Check Status Details
─────────────────────────────────────────
1. Run Discovery PASS Run 01KJY... found
2. Journal Integrity PASS 42 events, checksums valid
3. State Cache PASS Consistent
4. Effect Status WARN 1 stuck effect (> 30min)
5. Lock Status PASS No stale locks
...
Then print detailed findings and recommendations for any WARN/FAIL checks.