requesting-code-review

Dispatch a code-reviewer subagent to automate formal code review requests.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/Ramachandrajoshi/Azure-Devops-Copilot --skill requesting-code-review-ramachandrajoshi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/Ramachandrajoshi/Azure-Devops-Copilot/tree/main/.roo/skills/requesting-code-review
Command: npx skills add https://github.com/Ramachandrajoshi/Azure-Devops-Copilot --skill requesting-code-review-ramachandrajoshi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures code quality and consistency by delegating and recording formal code reviews early in the development workflow.

Core Features & Use Cases

  • Automates triggering a formal code-review process by dispatching a code-reviewer subagent after tasks or before merges.
  • Provides a structured feedback format with What Was Implemented, Plan/Requirements, and BASE/HEAD references, plus severity-based issue categorization.
  • Enables traceability and repeatability of reviews across multiple tasks and teams.

Quick Start

Dispatch the code-reviewer subagent to initiate a formal code review after completing a task or before merging.

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 reviews before merging a pull request?

You can automate code reviews by dispatching a code-reviewer subagent that captures base and head SHAs, then formats structured feedback with categorized issues to ensure production readiness before merging to main.

What is the best way to structure code review feedback for production readiness?

Structured code review feedback should include what was implemented, plan requirements, base and head SHA references, strengths, and severity-based issue categorization to ensure traceability and repeatability across tasks.

When should I trigger an automated code review in my git workflow?

Automated code reviews should be triggered after completing each task, after finishing major features, and before merging to main to catch issues early and maintain code quality throughout the git workflow.

How does a subagent code review process work for pull requests?

A subagent code review works by dispatching a templated code-reviewer process that captures base and head SHAs, evaluates the pull request changes, and returns formatted results with strengths and categorized issues.

Can I integrate automated code reviews into my existing git workflow without dependencies?

Yes, this code review automation operates with no external dependencies by dispatching a subagent directly within your existing git workflow to format and record review feedback before merges.

Why use a templated subagent for code reviews instead of manual reviews?

A templated subagent ensures consistent code review formatting, captures traceable base and head SHA references, and categorizes issues by severity, reducing human error compared to manual pull request reviews.