requesting-code-review

Dispatch a reviewer subagent to evaluate recent code changes.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/SlevoDev/s-tag --skill requesting-code-review-slevodev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/SlevoDev/s-tag/tree/main/.claude/skills/requesting-code-review
Command: npx skills add https://github.com/SlevoDev/s-tag --skill requesting-code-review-slevodev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates structured code-review requests by dispatching a dedicated reviewer subagent to evaluate recent changes.

Core Features & Use Cases

  • Dispatches a code-reviewer subagent to evaluate recent changes with precise, task-focused context.
  • Provides a structured feedback workflow that keeps the reviewer focused on the work product, not the session history.
  • Enforces review at key points: after each task and before merging to main, ensuring alignment with requirements and quality standards.

Quick Start

Request a code review after completing a task by dispatching the code-reviewer subagent with the relevant context.

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 a code review request for recent git pull request changes?

To automate code review requests, this Skill dispatches a dedicated reviewer subagent to evaluate recent git changes with precise, task-focused context, ensuring the review is focused on the work product rather than session history.

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

You should trigger a code review at key points in your workflow: immediately after completing each subagent-driven task and before merging major features into the main branch to ensure quality and alignment with goals.

What context do I need to provide to dispatch a code-reviewer subagent?

Dispatching a code-reviewer subagent requires a standardized review template, access to the relevant git SHAs for the recent changes, and a mechanism to route the review request to the appropriate reviewer subagent.

Does this code review workflow work with manual session history or only isolated pull requests?

This workflow is designed for isolated work products. It provides a structured feedback workflow that keeps the reviewer focused on evaluating the recent changes themselves, explicitly ignoring the broader session history.

What is the best way to ensure quality and alignment before merging a major feature?

The best way to ensure quality before merging is to enforce a structured code review by dispatching a reviewer subagent to evaluate the recent changes against requirements and quality standards.