requesting-code-review

Automating code review requests involves dispatching a code-reviewer subagent using Git commit SHAs and implementation requirements to verify code quality before merging. The subagent identifies changes through Git commit ranges and returns structured feedback categorized by severity.

The process involves providing Git commit SHAs to a code-reviewer subagent along with task requirements. The subagent analyzes the specified code range and returns categorized feedback identifying critical, important, and minor issues to address before merge.

The code-reviewer subagent provides structured feedback categorized by severity: Critical, Important, and Minor. This classification helps prioritize which identified issues to address first to ensure production readiness and adherence to quality standards.

Yes, you can specify a code range by providing the relevant Git commit SHAs to the code-reviewer subagent. The subagent evaluates the specified commit range against provided requirements to verify production readiness and adherence to quality standards.

You should request a code review after completing a feature or task but before merging. This facilitates early and frequent verification of work against requirements, preventing bugs and ensuring overall code health before integration into the main branch.

No specific external dependencies are required to use this skill. It operates using Git commit SHAs and a dedicated code-reviewer subagent to automate the verification process, requiring only your implementation details and task requirements to dispatch the review.