requesting-code-review

Automate code reviews with structured templates and base/head SHAs.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/tomasbasso/SistemaStockV2 --skill requesting-code-review-tomasbasso
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/tomasbasso/SistemaStockV2/tree/main/.agents/skills/solicitud-revision-de-codigo
Command: npx skills add https://github.com/tomasbasso/SistemaStockV2 --skill requesting-code-review-tomasbasso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines and standardizes code-review workflows to catch issues earlier, improving merge quality and team collaboration.

Core Features & Use Cases

  • Trigger an automated code-review prompt after code changes to surface issues before merging.
  • Provide a structured template with placeholders for what was implemented, plan/requirements, and base/head SHAs to guide reviewers.
  • Supports common scenarios like task completion, major feature work, or pre-merge checks to ensure compliance with requirements.

Quick Start

Dispatch the code-reviewer subagent with the necessary details to initiate a 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 reviews before a pull request merge?

Automated code reviews trigger after code changes to surface issues before merging. You provide the implemented changes, plan, and base/head SHAs to guide structured feedback and ensure compliance with requirements.

Can I enforce code quality and requirement conformance during the development workflow?

Code quality is enforced by running a guided review after each task or major feature. This process checks for issues against your original plan or requirements before the code is allowed to merge.

What do I need to provide to start an automated pull request review?

To start a pull request review, you need to specify the changes implemented, the base and head SHAs, and the plan or requirements. These details guide the reviewer feedback.

Is there a structured template for pre-merge code checks?

A structured template with placeholders for the implemented changes, plan or requirements, and base/head SHAs is provided. This standardizes the pre-merge checks and guides the reviewer feedback.

When should I trigger a code review in my development workflow?

Trigger a code review after completing a task or major feature work, specifically before merging. This timing ensures the code conforms to requirements and catches issues early.

What is the best way to standardize the review process for a new feature?

Standardizing the review process for a feature involves dispatching an automated code-reviewer with the specified changes, base/head SHAs, and requirements. This streamlines team collaboration and improves merge quality.