requesting-code-review

Dispatch a code-reviewer sub-agent with base/head SHAs and a review template.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/vincent-ng/OpenAgentArm --skill requesting-code-review-vincent-ng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/vincent-ng/OpenAgentArm/tree/main/.trae/skills/requesting-code-review
Command: npx skills add https://github.com/vincent-ng/OpenAgentArm --skill requesting-code-review-vincent-ng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Facilitates timely, structured code-review feedback by automatically dispatching a specialized code-reviewer sub-agent after task completion, preventing unchecked changes from slipping through the cracks.

Core Features & Use Cases

  • Template-driven review requests that enforce consistent feedback.
  • Capture and compare base/head SHAs to generate precise diffs for review.
  • Structured critique checklist guiding reviewers on code quality, architecture, and risks.
  • Use Case: Before merging critical features, trigger a reviewer to validate changes and surface issues early in the workflow.

Quick Start

After finishing a task, dispatch the code-reviewer sub-agent using the Task tool with the required base/head SHAs and the review template.

Frequently Asked Questions about requesting-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code review requests before merging a pull request?

Automate code review requests by dispatching a specialized code-reviewer sub-agent after task completion to enforce structured, pre-merge feedback on implemented changes. It uses a template to capture base and head SHAs and generate precise diffs for validation.

What is the best way to enforce a consistent quality-assurance checklist in a git workflow?

Enforce a consistent quality-assurance checklist by applying a template-driven review process that guides reviewers on code quality, architecture, and risks. This prevents unchecked changes from slipping through the cracks by capturing base and head SHAs for standardized critique.

How do I trigger a code reviewer after finishing a software development task?

Trigger a code reviewer after finishing a task by dispatching the sub-agent using the Task tool. You provide the required base and head SHAs along with the review template to validate changes and surface issues early in the workflow.

Does this automated code review process work across multiple software development tasks?

Yes, this automated code review process applies to software development workflows that require structured, pre-merge feedback on implemented changes across multiple tasks. It enforces a templated review process to ensure consistent quality and safety validation.

Why do I need to capture base and head SHAs for a pull request review?

Capture base and head SHAs to generate precise diffs for review and ensure accurate tracking of implemented changes. This templated approach enforces consistent feedback by providing the reviewer with exact before and after states of the code.

Are there limitations to using a sub-agent for structured code reviews?

Using a sub-agent for structured code reviews requires providing accurate base and head SHAs and depends on the Task tool to dispatch the reviewer. It functions as a pre-merge validation step and does not replace the human judgment needed for complex architectural decisions.