skills.rest
lightxue
lightxueCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

requesting-code-review

Route code changes through a dedicated code-review subagent using a structured template.

Updated Aug 23, 2026
Search Tags:#development#subagent#quality-assurance#code-review#pre-merge#review-workflow
One-click install
npx skills add https://github.com/lightxue/dotfiles --skill requesting-code-review-lightxue
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/lightxue/dotfiles/tree/main/agent/skills/requesting-code-review
Command: npx skills add https://github.com/lightxue/dotfiles --skill requesting-code-review-lightxue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures code changes are reviewed thoroughly and early, reducing defects and regressions before they reach main branches.

Core Features & Use Cases

  • Structured review workflow: routes tasks through a dedicated code-review subagent to surface issues with precise context.
  • Guided feedback templates: provides a consistent template (WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, DESCRIPTION) to standardize reviews.
  • Pre-merge guardrails: helps teams enforce mandatory reviews for major features and critical changes.

Quick Start

Review a recent task by dispatching the code-review subagent to evaluate your latest changes using the provided template.

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 to main?▼

Automate code reviews by routing changes through a dedicated code-review subagent to surface issues early. This enforces a structured template with base and head SHAs, implementation summaries, and requirements references before merging to main.

What is a pre-merge code review workflow and when do I need it?▼

A pre-merge code review workflow ensures changes are evaluated thoroughly before reaching main branches. You need it after implementing major features or completing tasks to reduce defects and regressions early.

How do I standardize code review feedback for major features?▼

Standardize code review feedback by enforcing a guided template capturing WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION. This provides consistent context for evaluating major features.

Can I use a subagent to review code changes after each task?▼

Yes, you can dispatch a code-review subagent to evaluate changes after each task. It provides precise context for evaluation, preserving developer focus while routing changes through formal pre-merge guardrails.

Does a structured code review workflow help prevent regressions?▼

A structured code review workflow helps prevent regressions by routing changes through a dedicated subagent to surface issues early. Pre-merge guardrails enforce mandatory reviews for critical changes before they reach main branches.

What's the best way to provide context for evaluating code changes?▼

The best way to provide context for evaluating code changes is using a formal template with base and head SHAs, a summary of what was implemented, and a plan or requirements reference to guide feedback.

Related Skills

Explore More Software Engineering Skills→
haidonglethqbhaidonglethqb

code-review

Define code-review scope and trigger verification steps across impacted files.

Community
Advanced
lshtramlshtram

finish-task

Verify code quality and merge feature branches into main.

Community
Intermediate
ZJUxjyZJUxjy

requesting-code-review

Dispatch a subagent to analyze code changes against requirements and quality standards.

Community
Intermediate
RangeyRoverRangeyRover
3

speckit.checker

Run static analysis across multiple languages and generate prioritized issue reports.

Community
Intermediate