Skip to main content
Run doctor first whenever you experience unexpected behavior. It quickly surfaces missing directories, unparseable recipes, a stale lockfile, and absent tooling before you dig deeper.
The doctor command inspects your local setup and reports the status of each check:

​
Checks performed

Each check reports either ok or warn. A warn result does not stop the tool from running, but it may explain unexpected behavior. process_lock reports warn when the lockfile looks stale or malformed. That usually means a previous run exited unexpectedly, and the next run can clean it up. doctor checks local files, local tools, and performs a lightweight request to the GitHub API to verify your rate limit and token status.
Add --json to get machine-readable output suitable for scripting or monitoring:

​
Common issues

Recipe files failed to parse Run validate to identify which files have errors and what the parse error is:
To check a single recipe by name:
Config directory not found Initialize the configuration directory with:
This creates the expected directory structure and a starter config.yml.
Last modified on April 18, 2026