Code Review Now Judges Your Whole Staged Plan
Reviewing a pull request from a staged breakdown now considers the entire parent-and-sub-task plan, not just the one task's isolated change.
Summary
Reviewing a pull request that belongs to a staged breakdown of parent and sub-tasks now weighs the whole plan, not just that one task in isolation — so review feedback matches how the work was actually meant to be split up.
What You Gain
When a task is one stage in a larger breakdown, judging its pull request alone could produce the wrong call: flagging it as incomplete for work a later stage was always meant to handle, or approving it even though it quietly contradicted something an earlier stage already shipped. Now the reviewer sees every related task in the breakdown — its stage, its status, and how it fits in — before judging the change in front of it. This extends review to understand staged breakdowns the same way the rest of Effigate already does.
How It Works
- Full-family context. The reviewer reads the parent and every sibling sub-task's description and history before judging any one pull request.
- The right standard. Missing work that belongs to a later stage is no longer flagged as incomplete; contradicting an earlier stage's work still is.
- Bypass detection. If a parent's own pull request tries to absorb work that should have gone through its sub-tasks, the review now catches it and sends it back, instead of letting it merge.
Where to Find It
This applies automatically to every code review on a task that's part of a staged breakdown; nothing to configure.
See what else shipped that month on the Effigate Command Center changelog, or try Effigate Command Center.