01
Self-enforcing standard.
Reading thresholds defined in one config. The team self-corrects against the check, not against you.
For engineering leaders
Approval, with the work behind it.
You can feel the bar dropping. PRs the size of a feature shipping in under a minute of review time. Read PR puts a measurable floor under the act of reading — without making it your job to enforce.
What you keep saying out loud.
- I am the only person on the team who still opens the file.
- AI is making more code than the team can review honestly.
- I do not want to make this a hallway conversation again.
- I want approval to mean something, not be a culture campaign.
What changes after you install.
02
No surveillance read.
Reviewers prove they read it. The framing is positive. No leaderboards, no public callouts, no dark patterns.
03
A signal you can trust.
Approval times stop being noise. The reading record under each one is the actual work.
Make the next approval mean something.
Two minutes to install. Free for public repos. The first private repo is on us.