The quality gate for the agent era

Your agents write code. developer-doctor proves it meets your standard.

Everyone has an AGENTS.md now. Almost no one has a gate that checks the agent actually followed it. One npx, one 0–100 score across 18 engineering categories. Your rubric lives in a private oracle — your agents can’t game what they can’t read.

$ npx developer-doctor . or install into your agent →
developer-doctor — health check
$ npx developer-doctor .
0scanning
health score · 0–100
BLOCK IMPORTANT ADVISORY

Why now

AI-assisted coding scaled faster than the quality controls around it.

DORA 2025
+154%

PR size. After a 90% rise in AI-coding adoption: +91% review time, +9% bug rate. The volume went up. The quality did not.

Faros AI 2026 · 22,000 devs
31%

of AI PRs merge with zero human review. Review time is up 441%. Someone has to be the last line of defence.

CodeRabbit · Dec 2025 · 470 PRs
1.7×

more issues in AI-written code than human code — readability 3×, performance 8×. The gap is not closing on its own.

The shift

“Telling an agent ‘follow our standards’ is probabilistic compliance. Wiring a gate that blocks the PR when standards are violated is deterministic enforcement.”
Augment Code

developer-doctor is the deterministic gate.

The moat

Not a linter. Not a dashboard. Not another AI reviewer.

01 · PRIVATE ORACLE

Your standard, uncloneable

The rubric and per-check weights live server-side. The CLI ships only a finder — it emits coded findings, never the logic behind them. No competitor keeps the standard out of the repo, so no competitor’s gate is un-gameable.

02 · ONE NUMBER

0–100 across 18 categories

Code, docs, delivery, git hygiene, containers, CI, security, testing, observability, and LLM/agent practice — scored into one number a script can compare. Own the health number the way Lighthouse owns web performance.

03 · THE RATCHET

Fails on regression, not a threshold

The gate blocks the PR when the score drops below your team’s prior best — not a fixed number teams quietly lower. It runs where agents already live: MCP, Claude Code hooks, GitHub Action, AGENTS.md.

How it works

Audit. Gate. Let the agents fix themselves.

01

Audit anything

Zero install, no config. A 0–100 score and tiered findings in seconds. Works offline.

$ npx developer-doctor .
02

Set the baseline, gate every PR

init scaffolds a CI workflow, a README score badge, and a committed baseline. From then on, --gate fails the build on any regression.

$ npx developer-doctor init  &  npx developer-doctor . --gate
03

Agents self-correct

install injects the gate skill into AGENTS.md, CLAUDE.md, and .cursorrules, and registers a Claude Code Stop hook. Every agent runs the audit before it opens a PR — and blocks itself on a regression.

$ npx developer-doctor install --hooks

In the box

Everything runs from one zero-dependency CLI.

Install into every agent

Teach Claude Code, Cursor, Copilot, and Windsurf to run the gate before every PR.

developer-doctor install --hooks

Roast + shareable scorecard

A humor-tinged reading, plus an SVG scorecard you can drop in a PR or a tweet.

developer-doctor roast --card card.svg

Per-agent scorecard

Which agent — Claude Code, Cursor, Codex, Copilot — actually meets your standard? Nothing else answers this.

developer-doctor agents

Bring your own standard

Encode your team’s rules as checks in dd.standard.json — enforced on every run.

developer-doctor standard init

MCP server

Any coding agent in your stack can call the audit directly and fix before committing.

developer-doctor mcp

Reports & badges

Self-contained HTML or Markdown reports, plus a live shields.io score badge.

developer-doctor . --report html

Real scores

We scored ten beloved OSS repos. The median was 30.

Real offline scores under the strict 18-category standard. Large codebases accumulate advisory candidates — a 46 doesn’t mean Express is broken, it means there are 54 points of room before your agents ship on top of it. A breadth-of-standard story, not a quality verdict.

chalk
56
execa
51
commander
49
express
46
flask
35
requests
17
date-fns
16
hono
11
zod
8
fastapi
6

Median ~30 / 100. CodeScene found codebases below 9.5/10 health make AI agents introduce 60% more defects and burn 50% more tokens. Your agents start from a low baseline — the ratchet stops them from making it worse.

Where it fits

Honest about the neighbours.

Capabilitydeveloper-doctorLintersSonarQubeAI reviewersOSSF Scorecard
One 0–100 health scorepartial
18-category spanone languagesecurity only
Private, un-gameable rubric
Ratchet on regressionfixed gate
Agent-loop / MCP nativeadded-onper-diff
Zero-install (npx)

Linters, SonarQube, CodeRabbit, and OpenSSF Scorecard are each excellent at what they do — one language’s syntax, deep SAST, per-diff review, supply-chain security. developer-doctor is the layer none of them are: one private, unified standard, enforced inside the agent loop. Drop it into any agent runner or CI pipeline — they route the work; developer-doctor is the gate that says whether it met your standard.

Your standard. Their code. Your gate.

In ten seconds you’ll know how far your code is from your own bar.

In one command you’ll block every agent, on every PR, from making it worse.

$ npx developer-doctor . $ npx developer-doctor install