requesting-code-review

To generate a structured code-review request, invoke the code-reviewer subagent to populate a template capturing implemented work, plan requirements, and starting and ending git SHAs. This enforces consistent, prioritized feedback before merging to main.

You should request a code review after completing individual tasks, finishing major features, and validating pre-merge changes. This task-driven code review process ensures timely feedback and higher quality changes across your software projects.

The best way to standardize pull request reviews is to use a structured template guiding reviewers to categorize issues by severity. This enforces standard placeholders for implemented work, requirements, and git SHAs to ensure clear feedback.

Yes, this code review workflow requires the starting and ending git SHAs to define the scope of changes. Providing these git SHAs ensures the code-reviewer subagent evaluates the correct commit range for accurate pre-merge validation.

Yes, you can use this code review template after major feature completion. It supports task-driven development by collecting implemented work and plan requirements to provide actionable, prioritized feedback for your software projects.

A limitation of automating code-review requests is that it requires manual input of plan requirements and git SHAs. The skill relies on the code-reviewer subagent, meaning it standardizes the request format rather than fully automating the review itself.