doctor-report

name	doctor-report
description	Run the repo’s environment and dependency diagnostics as a JSON-stdio skill so Claude Code or Codex can capture a health report instead of scraping CLI stderr.
allowedTools	["shell","read","write"]
model	inherit
argumentHint	{"strict":false,"outputPath":"output/content-machine/doctor/doctor.json"}
entrypoint	node --import tsx scripts/harness/doctor-report.ts
inputs	[{"name":"strict","description":"Fail warnings as well as hard errors.","required":false},{"name":"outputPath","description":"Path for the doctor report file.","required":false},{"name":"outputDir","description":"Directory for run-scoped report.json when outputPath is not set.","required":false}]
outputs	[{"name":"doctor.json","description":"Doctor report containing the check list and top-level ok status."}]

Doctor Report

Use When

• Claude Code or Codex needs an environment health report before attempting generation work.
• The agent wants JSON diagnostics instead of parsing the legacy cm doctor human output.
• Local automation needs a stable ok plus check-count summary.

Invocation

cat <<'JSON' | node --import tsx scripts/harness/doctor-report.ts
{
  "strict": false,
  "outputPath": "output/content-machine/doctor/doctor.json"
}
JSON

Output Contract

• Runs the same core doctor checks used by the legacy CLI.
• Writes one JSON report file to outputPath, or to outputDir/report.json when a flow binds a run-scoped output directory.
• Returns a JSON envelope with ok, strict mode, and warning/failure counts.

Validation Checklist

• The resolved report path exists.
• The report contains a top-level ok boolean and a checks array.
• Failure and warning counts in the envelope match the file.