requesting-code-review

Automate peer review initiation and template-based feedback collection for code changes across Git workflows.

1|Updated Jan 5, 2023
One-click install
npx skills add https://github.com/riez/dots --skill requesting-code-review-riez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/riez/dots/tree/main/.config/agentic/skills/requesting-code-review
Command: npx skills add https://github.com/riez/dots --skill requesting-code-review-riez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams ensure code quality and alignment before merging by automating and standardizing code-review requests, reducing blind spots and rework.

Core Features & Use Cases

  • Dispatch code-reviewer subagent to review changes before merging.
  • Capture and structure feedback using a consistent template with WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, and HEAD_SHA.
  • Integrate with existing workflows to enforce reviews after each task or major feature.

Quick Start

Dispatch the code-reviewer subagent for your latest changes and provide the implemented details and baseline commits to start the review.

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 for pre-merge verification in Git?

Automate code review requests by dispatching a code-reviewer subagent with your BASE_SHA, HEAD_SHA, and implementation details to generate structured feedback for pre-merge verification.

What do I need to provide to initiate a structured code review for my feature implementation?

To initiate a structured code review, you need to provide the BASE_SHA and HEAD_SHA of your changes, along with a clearly described WHAT_WAS_IMPLEMENTED and PLAN_OR_REQUIREMENTS.

Does this code review automation work with task-driven development workflows?

Yes, this code review automation applies to task-driven development, feature implementation, and pre-merge verification across Git workflows by enforcing reviews after each task.

What is the best way to catch issues early before merging code changes?

The best way to catch issues early is to standardize code-review requests using a template-based feedback collection system that dispatches a code-reviewer subagent before merging.

Why should I use a subagent to collect feedback on code changes instead of manual review?

Using a subagent to collect feedback reduces blind spots and rework by capturing and structuring feedback consistently, ensuring code quality and alignment before merging changes.

What limitations exist when applying template-based feedback collection to code changes?

Limitations include the strict requirement for baseline and head commit SHAs plus documented implementation details; without these inputs, the code-reviewer template cannot generate structured feedback.