prokodo doctor

Check your environment health before running verifications.

prokodo doctor [global options]

Checks performed

Check	What it verifies
Node version	Node.js ≥ 22 is installed
API key configured	At least one key source is available (flag / env var / file)
.prokodo/config.json	A valid config file exists in the current working directory
API reachability	The prokodo API health endpoint responds within 10 seconds
API key valid	(Only if a key is present) The key is accepted by the API

Examples

# Text output with colour-coded icons
prokodo doctor

✓  Node version               22.11.0 (required ≥ 22)
✗  API key configured         Source: none
✗  .prokodo/config.json       Config not found in /Users/you/my-project
✓  API reachability           https://www.n8n-marketplace.prokodo.com → OK (v1.2.3)

# Machine-readable JSON — perfect for CI notifications
prokodo doctor --json

{
  "passed": false,
  "checks": [
    { "name": "Node version", "passed": true, "detail": "22.11.0 (required ≥ 22)" },
    { "name": "API key configured", "passed": false, "detail": "Source: none" },
    {
      "name": ".prokodo/config.json",
      "passed": false,
      "detail": "Config not found in /Users/you/my-project"
    },
    {
      "name": "API reachability",
      "passed": true,
      "detail": "https://www.n8n-marketplace.prokodo.com → OK (v1.2.3)"
    }
  ]
}

Exit codes

Code	Cause
0	All checks passed
1	One or more checks failed

tip

doctor never exits 2 — it is designed to always produce output. Use it in CI to surface problems early:

- name: Environment health check
  run: prokodo doctor --json
  continue-on-error: true # report, don't fail the pipeline

Use in CI

- name: prokodo doctor
  run: |
    OUTPUT=$(prokodo doctor --json)
    echo "$OUTPUT" | jq .
    echo "$OUTPUT" | jq -e '.passed'   # fails pipeline if not all checks pass

Verbose mode

Add --verbose to see debug-level detail on stderr while the checks run:

prokodo doctor --verbose