A Review Verdict Moves the Task and Brings the Author Back
Approving or requesting changes on a pull request now moves and labels its task automatically, and sends rework straight back to the author.
Summary
A code review used to end with a comment and a clear approve-or-request-changes verdict, but no visible effect on the task itself — so you couldn't tell from the board what had actually been reviewed or who it was waiting on. A review verdict now does something: it moves the task to the right column, labels it clearly, and if changes are needed, sends the findings straight back to the agent that wrote the code so it can fix them.
What You Gain
Previously, knowing whether a task's code had been reviewed, and what the outcome was, meant opening the task and reading through comments yourself. The board gave no clue, and when a review asked for changes, nothing automatically told the original agent to go fix them — someone had to notice and re-trigger that work by hand.
Now the outcome of a review is visible at a glance. An approval moves the task to In Review with a clear label. A request for changes moves it back to To Do, posts the findings as a comment addressed directly to the agent that wrote the code, and queues that agent to make the fix — if the agent is already busy, the fix waits in line rather than getting dropped.
How It Works
- A verdict labels and moves the task automatically the moment it lands, not buried in a comment thread.
- Rework goes straight back to the author, which is told exactly what to fix and queued to do it.
- The author hands it back cleanly. Once the agent pushes its fix, the task returns to review and the same reviewer looks at the new version.
- Repeated rounds come to you. Two rounds re-trigger automatically; the third is handed to you to decide.
- The review labels can't be set or removed by hand — only an actual verdict changes them.
- You can still step in and review something yourself at any point from the pull request.
Where to Find It
This applies automatically to any project using agent-driven code review — there's nothing to turn on. Review verdicts and their effect on the task are visible directly on the task and its pull request.
See what else shipped that month on the Effigate Command Center changelog, or try Effigate Command Center with your own team.