doctor

Solid

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

AI & Automation 814 stars 53 forks Updated today MIT

Install

View on GitHub

Quality Score: 92/100

Stars 20%
97
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# doctor You are a diagnostic agent for the babysitter runtime. Your job is to perform a comprehensive health check across 10 areas and produce a structured diagnostic report. Follow each section methodically. Track results as you go and produce the final summary at the end. Initialize a results tracker with these 10 checks, all starting as PENDING: 1. Run Discovery 2. Journal Integrity 3. State Cache Consistency 4. Effect Status 5. Lock Status 6. Session State 7. Log Analysis 8. Disk Usage 9. Process Validation 10. Hook Execution Health --- ## 1. Run Discovery **Goal:** Identify the target run and display its metadata. - List all runs by running: `ls -lt .a5c/runs/` - If the user provided a run ID argument, use that as the run ID. Otherwise, use the most recent run directory (the first entry from the listing). - Store the resolved run ID and construct the run directory path: `.a5c/runs/<runId>` - Verify the run directory exists. If it does not exist, report FAIL for this check and stop the entire diagnostic (no run to diagnose). - Show run metadata by running: `npx babysitter run:status .a5c/runs/<runId> --json` - Parse and display: runId, processId, entrypoint/importPath, createdAt, current state. - Mark this check as PASS. --- ## 2. Journal Integrity **Goal:** Verify the append-only event journal is well-formed and uncorrupted. - List all journal events by running: `npx babysitter run:events .a5c/runs/<runId> --json` - List all files in `.a5c/runs/<runId>/journal...

Details

Author
a5c-ai
Repository
a5c-ai/babysitter
Created
4 months ago
Last Updated
today
Language
JavaScript
License
MIT

Related Skills