requesting-code-review

Name: requesting-code-review
Availability: InStock
Author: artgaurav16420-oss

Dispatch a code-reviewer subagent to review changes between git revisions.

Updated May 2, 2026

Search Tags:#workflow #subagent #quality-assurance #code-review #pull-request #review-template

Ready to run

npx skills add https://github.com/artgaurav16420-oss/Mega-Skills --skill requesting-code-review-artgaurav16420-oss

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/artgaurav16420-oss/Mega-Skills/tree/main/distribution/harnesses/tabnine/agent/skills/requesting-code-review
Command: npx skills add https://github.com/artgaurav16420-oss/Mega-Skills --skill requesting-code-review-artgaurav16420-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dispatch code-reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation — never your session's history. The reviewer focuses on the work product, preserving your own context for continued work.

Core Features & Use Cases

Automated reviewer workflow: Initiates a code-review using a standardized template to ensure consistency.
Template-driven feedback: Uses the code-reviewer.md template and placeholders to produce actionable guidance for developers.
Pre-merge quality gate: Validates changes before merging, reducing risk of regressions.

Quick Start

Dispatch a code-reviewer subagent to evaluate the latest changes 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?▼

Automate code reviews by dispatching a code-reviewer subagent to evaluate changes using a standardized template. This initiates a pre-merge quality gate to catch issues and reduce regression risk before integration.

What is template-driven code review and how does it work?▼

Template-driven code review uses a standardized template with placeholders to produce actionable guidance. A subagent evaluates work product against this template, ensuring consistent feedback without polluting your working session context.

How do I run a pre-merge quality gate on task-driven feature implementation?▼

Run a pre-merge quality gate by providing a base and head git revision along with an aligned task plan. The reviewer subagent evaluates the specific changes and outputs structured feedback to validate the feature implementation.

Do I need a specific git revision range to request a code review?▼

Yes, requesting a code review requires a base and head git revision to define the scope. You also need an aligned task plan so the reviewer subagent has precisely crafted context for evaluation.

Can I use a subagent to review code without losing my current session context?▼

Yes, dispatching a code-reviewer subagent provides precisely crafted context for evaluation rather than your session history. The subagent focuses solely on the work product, preserving your own context for continued development.

What are the limitations of automating pull request reviews with a subagent?▼

The approach is limited to task-driven development and pre-merge review across a codebase. It requires an aligned task plan and specific git revisions, meaning it cannot evaluate changes lacking defined base and head revisions.