babysitter:doctor

Diagnose babysitter run health — journal integrity, state cache, effects, locks, sessions, logs, and disk usage.

509 stars

Best use case

babysitter:doctor is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Diagnose babysitter run health — journal integrity, state cache, effects, locks, sessions, logs, and disk usage.

Teams using babysitter:doctor should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/doctor/SKILL.md --create-dirs "https://raw.githubusercontent.com/a5c-ai/babysitter/main/plugins/babysitter-codex/.codex/skills/babysitter/doctor/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/doctor/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How babysitter:doctor Compares

Feature / Agentbabysitter:doctorStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Diagnose babysitter run health — journal integrity, state cache, effects, locks, sessions, logs, and disk usage.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# babysitter:doctor

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).

## Run Discovery

If no run-id argument provided, find the most recent run:
```bash
ls -t .a5c/runs/ | head -1
```

## 10 Mandatory Health Checks

For each check, report **PASS**, **WARN**, or **FAIL**.

### 1. Run Discovery
- Verify run directory exists at `.a5c/runs/<runId>/`
- Display run metadata (process ID, created at, status)
- Check manifest.json exists and is valid

### 2. Journal Integrity
- Verify `.a5c/runs/<runId>/journal.jsonl` exists
- Check each line is valid JSON
- Verify timestamps are monotonically increasing
- Verify event type consistency
- Count events by type

### 3. State Cache Consistency
- Compare `state.json` against journal events
- Verify derived state matches journal history
- Check for orphaned state entries

### 4. Effect Status
- List all effects and their statuses
- Flag stuck effects (requested > 30 minutes ago, still pending)
- Flag errored effects
- Count pending vs completed

### 5. Lock Status
- Check for `run.lock` file
- If lock exists, verify PID is alive
- Flag stale/orphaned locks

### 6. Session State
- Inspect session state file
- Check iteration count vs max
- Detect potential runaway loops (fast iteration pattern)

### 7. Log Analysis
- Check `.a5c/logs/` for hook logs
- Scan for errors in stderr logs
- Report log file sizes

### 8. Disk Usage
- Report `.a5c/runs/<runId>/` total size
- Identify files > 10MB
- Report blob storage usage

### 9. Process Validation
- Verify process entry point exists and passes `node --check`
- Check `@a5c-ai/babysitter-sdk` dependency is installed
- Verify process exports match manifest

### 10. Hook Health
- Check all hook scripts exist and are executable
- Verify `sh -n` passes for shell scripts
- Verify `node --check` passes for JS hooks

## Output

Print 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.

Related Skills

babysitter

509
from a5c-ai/babysitter

Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)

doctor

509
from a5c-ai/babysitter

Diagnose Babysitter run health, integration issues, or orchestration failures.

babysitter:issue

509
from a5c-ai/babysitter

Start a babysitter workflow from a GitHub issue.

babysitter:help

509
from a5c-ai/babysitter

Help and documentation for babysitter commands, processes, skills, agents, and methodologies.

babysitter:assimilate

509
from a5c-ai/babysitter

Assimilate an external methodology, harness, or specification into babysitter process definitions.

babysitter:forever

509
from a5c-ai/babysitter

Start a never-ending babysitter run with infinite loops and sleep gates.

babysitter:plan

509
from a5c-ai/babysitter

Plan a babysitter workflow without executing it. Focus on creating the best process possible.

babysitter-codex

509
from a5c-ai/babysitter

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".

babysitter:user-install

509
from a5c-ai/babysitter

Set up babysitter for yourself. Install deps, build user profile, configure tools.

babysitter:retrospect

509
from a5c-ai/babysitter

Analyze a completed or in-flight run and propose process improvements for future runs.

babysitter:observe

509
from a5c-ai/babysitter

Launch the babysitter observer dashboard for real-time run monitoring.

babysitter:yolo

509
from a5c-ai/babysitter

Start babysitting in non-interactive mode — no user interaction or breakpoints, fully autonomous execution.