ferrox-requesting-code-review

To review a git diff against requirements before merging, provide a precise commit range so the reviewer can evaluate implementation accuracy, architecture, testing, and readiness without session history influence.

Pre-merge code review in subagent-driven development validates each completed task increment against the original plan to catch bugs, requirement gaps, and design mistakes before they cascade into later work.

Yes, you can use a quality gate to check production readiness for refactoring changes by inspecting the exact git diff range to verify implementation accuracy, architecture, and testing.

Validate completed feature increments task-by-task by handing the reviewer the exact commit range and requirements for read-only inspection of the diff against the plan.

Yes, you need a precise git diff range to perform a code review, ensuring the evaluation focuses strictly on the completed changes without being influenced by the rest of your session history.