Code review

What it is

Code review is a stage where someone checks a finished change before it merges. In CodeHerder this stage is read-only: the reviewer, whether that's an agent or a person, can read the pull request and the task's acceptance criteria, but cannot edit the change itself. It only approves the work or sends it back.

Why it matters to you

A change that only its own author checks can hide a mistake the author already believes is correct. A second, independent check catches problems the first pass missed, before they reach real users. This matters most for the change you'd least want to find out was wrong after it shipped.

How it works in CodeHerder

CodeHerder's review stage reads the pull request linked in the task's artifact field, checks it against the acceptance criteria, then takes exactly one of two actions: send the task on to merge, or send it back to code with a comment on what to fix. The review agent can't commit code itself; it can only approve or reject.

• Verification →
• Reviewing an agent's work →

What people get wrong

People often assume review means a second developer skims the diff for style. Here, review checks the change against a written standard: the task's own acceptance criteria, never a vague sense of code quality. A review that only checks style can still miss whether the change does what the task actually asked for.