requesting-code-review

You can automate code review requests by dispatching a review subagent that gathers changes, intended functionality, and relevant diffs to verify work against requirements before merging. This ensures production readiness by acting on findings from the structured review.

The best way to verify code changes against requirements is to trigger an automated review at key development milestones. The review subagent gathers context including diffs and intended functionality, providing structured feedback on architecture and testing.

Yes, you can use this automated code review skill for major feature implementations. It is specifically designed to be used when completing tasks or implementing major features to verify work against original requirements before merging.

The code review subagent gathers context for quality assurance by collecting the intended functionality, relevant git diffs, and original requirements. It uses this context to provide a structured checklist assessing code quality, architecture, and testing.

Yes, you need to provide a git range to request a code review. The skill uses this git range to identify the changes, allowing the review subagent to gather the relevant diffs and verify the implementation against the stated requirements.