DevDoctor Documentation

Read-only by default

Find project health issues before they become debugging sessions.

Start with a local command, move the same checks into CI, then automate against stable JSON, SARIF, baselines, and issue codes.

30+diagnostic modules

v1stable schema

3output formats

Install DevDoctor from source, Composer, PHAR, standalone binaries, GitHub Action, or Homebrew.

Use focused commands locally, devdoctor presets for stack detection, or devdoctor ci for non-interactive checks.

See command reference

Generate devdoctor.yml, tune env rules, and keep project-specific policy explicit.

Open config docs

Use practical paths for Laravel, frontend, monorepos, and CI rollout with baselines.

Open scenarios

PHPcore Node/frontendweb Pythonpy Ruby/Railsrb Gogo Rustrs Java/JVMjvm .NETcs C/C++cc Kubernetesk8s Terraform/IaCiac Mobileapp

Use JSON, SARIF, baselines, and pinned CI examples for repeatable automation.

Open CI examples

Choose table output for humans, JSON for tooling, or SARIF for code scanning.

Compare formats

Adopt DevDoctor in existing projects without hiding new warnings and errors.

Read baseline docs

Browse stable identifiers by module without opening the machine-readable JSON catalog.

Browse issue codes

Review the read-only contract, redaction behavior, and command execution boundaries.

Read safety docs

Review schema v1, issue code policy, and compatibility expectations.

Verify PHAR checksums, signed artifacts, and pinned release usage.

Verify releases

Track every tagged release from the Laravel Zero scaffold through the current multi-stack diagnostics set.

View changelog