Code review
Code Reviewer
Stands in for
The senior engineer who would review every pull request before it ships.
What it does
A bug is cheapest to catch before it ships and most expensive after, but a careful review is the step a stretched team drops first. The Code Reviewer reads each change your developers propose, in git, the way a senior engineer would, and writes a plain review: what looks wrong, what could break, what is risky, and what to fix, with the reasoning for each point.
It is built to help, not to nitpick. It separates the must-fix from the nice-to-have, explains why in terms a reviewer can act on, and points at the exact lines. It reviews and advises; it never merges, never changes your code on its own, and never approves its own suggestions. A person still makes the call.
Its routines
Each weekday
- Change review Reads each proposed change and writes up bugs, risks and fixes with line references.
- Severity sort Separates must-fix problems from style and nice-to-haves.
- Security pass Flags insecure patterns, exposed secrets and risky inputs.
- Test-coverage note Points out changes that ship without a test to cover them.
Once a week
- Repeat-issue note Flags the same mistake recurring, so it can be fixed at the source.
- Standards digest Keeps a short, current note of the review standards it applies.
Once a month
- Debt review Summarizes the risk and shortcuts building up across the codebase.
What it drafts for you
- A written review on every proposed change
- A must-fix versus nice-to-have split
- Security and missing-test flags
- A monthly technical-debt summary
What it won’t do
It never…
- Merge, push or change code on its own
- Approve a change for release
- Touch anything outside the change under review
Its first week
- Day 1: you give it read access to the repo and your coding standards.
- Days 2 to 3: it reviews recent changes and your team weighs its calls.
- Day 4: it tunes severity to match what your team actually cares about.
- End of week: you decide which checks it should run on every change going forward.
Good for
- Small dev teams with no senior reviewer to spare
- Agencies shipping client code on deadlines
- Solo developers who want a second set of eyes
The full version is in the course
The course shows you how to set this employee up and check its work.
The AI Masterclass teaches you to set up employees like this one and check their work. The plans start free.