skills.rest
Donaldshen27
Donaldshen27COMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

Review code changes before merging with Git SHA tracking.

Updated Nov 14, 2025
Search Tags:#git#workflow#templates#quality#subagent#code-review#review-process
One-click install
npx skills add https://github.com/Donaldshen27/xtrend-vanilla --skill requesting-code-review-donaldshen27
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/Donaldshen27/xtrend-vanilla/tree/main/.claude/skills/requesting-code-review
Command: npx skills add https://github.com/Donaldshen27/xtrend-vanilla --skill requesting-code-review-donaldshen27

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Effective code reviews are often delayed or inconsistent in fast-moving teams. This Skill standardizes the process by guiding users to request inspections using a dedicated reviewer subagent, ensuring early feedback and reduced risk.

Core Features & Use Cases

  • Enforces early review after each task, major feature completion, or before merging to main.
  • Provides templates and a clear workflow to dispatch the code-reviewer subagent with BASE_SHA, HEAD_SHA, and a description.
  • Supports adoption across task-driven development, refactoring, and incident fixes to maintain quality and accountability.

Quick Start

Dispatch the code-reviewer subagent after you complete a task, supplying the BASE_SHA, HEAD_SHA, and a brief description.

Frequently Asked Questions about requesting-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I request a code review for my latest git commits before merging?▼

To enforce consistent code reviews, dispatch a reviewer subagent with the BASE_SHA, HEAD_SHA, and a task description. This standardizes the workflow and captures feedback early across tasks, features, and bug fixes.

When should I initiate a code review in a subagent-driven development workflow?▼

You should initiate a code review after completing each task, major feature, or before merging to main. Requesting reviews at these milestones enforces early feedback and reduces risk in fast-moving teams.

What information do I need to provide to trigger a code review subagent?▼

You need to provide the BASE_SHA, HEAD_SHA, and a brief description of the code changes. Supplying these Git SHA references and context allows the subagent to accurately identify and review your changes against requirements.

Can I use this code review workflow for refactoring and incident fixes?▼

Yes, you can apply this workflow to refactoring and incident fixes to maintain quality and accountability. It supports adoption across task-driven development and incident fixes by enforcing review steps and templates.

Why does my team need a standardized code review template and process?▼

A standardized code review template and process solves the problem of delayed or inconsistent feedback in fast-moving teams. It guides users to dispatch inspections using a dedicated reviewer subagent, ensuring reduced risk and consistent quality.

Related Skills

Explore More Software Engineering Skills→
alffeialffei
69

requesting-code-review

Dispatch a code-reviewer subagent to validate git changes before merging.

Community
Intermediate
peancharoenpeancharoen

speckit.reviewer

Review git diffs and file paths for code issues with severity labels.

Community
Intermediate
limaonlimaon

subagent-driven-development

Dispatch fresh subagents per task with two-stage reviews.

Community
Advanced
MatthieuszMatthieusz

coding-standards

Validate TypeScript code against predefined coding standards using static analysis tools.

Community
Advanced