Standards as guardrails

One rulebook scans every diff. Slide the rulebook looser or stricter and watch how many lines it catches.

The problem this replaces

Two developers, two different bars

Same kind of change, two different reviewers, two different bars — one gap slips through.

How it works

The scanner never skips a line — it just routes each finding to whoever should act on it.

The rulebook is the team's own standards doc, loaded fresh every run — not a generic linter's opinion.

See it in action

diff: add-customer-export → blocking: any type → auto-fixed → warning: no test → PR note → PR opened

The blocking issue never reaches you. The warning does — as a note, not a surprise.

So what

The review bar is the same whoever ran the pipeline.