skills.rest
erikstmartin
erikstmartinCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

requesting-code-review

Dispatch a code-reviewer subagent with BASE_SHA and HEAD_SHA for feedback.

16|9|Updated Nov 6, 2013
Search Tags:#workflow#templates#quality#subagent#code-review#pull-request#review-process
One-click install
npx skills add https://github.com/erikstmartin/dotfiles --skill requesting-code-review-erikstmartin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/erikstmartin/dotfiles/tree/main/skills/global/.agents/skills/requesting-code-review
Command: npx skills add https://github.com/erikstmartin/dotfiles --skill requesting-code-review-erikstmartin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the code-review process by providing a clear, repeatable protocol for requesting and handling feedback before merging changes.

Core Features & Use Cases

  • Establishes when to request a review (after each task, after major features, before merging) and when optional reviews add value (when stuck or before refactoring).
  • Defines how to collect and forward changes with BASE_SHA and HEAD_SHA, and how to dispatch a dedicated code-reviewer subagent to evaluate the work.
  • Provides a structured template-driven feedback loop that helps teams maintain quality and consistency across reviews.

Quick Start

Obtain BASE_SHA and HEAD_SHA, dispatch the code-reviewer subagent with the proper template, and address the feedback accordingly.

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 before merging changes?▼

To request a code review, obtain the BASE_SHA and HEAD_SHA of your changes, then dispatch the code-reviewer subagent using the Task tool with the code-reviewer.md template to receive structured feedback.

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

Request a code review after completing each task, finishing major features, and before merging changes. Optional reviews are also recommended when you are stuck or before refactoring code.

What is the best way to structure pull request feedback for consistency?▼

The best way to structure pull request feedback is using a template-driven feedback loop, dispatching a code-reviewer subagent to populate the code-reviewer.md template for consistent quality checks.

How does a code-reviewer subagent evaluate changes between commits?▼

A code-reviewer subagent evaluates changes by receiving the BASE_SHA and HEAD_SHA references, which define the diff range, allowing it to assess the specific code modifications and populate the review template.

Can I use this code review process when stuck on a task?▼

Yes, you can use this code review process when stuck. Requesting an optional review provides structured feedback that can help identify issues or guide your next steps before refactoring or proceeding.

Related Skills

Explore More Software Engineering Skills→
JoeCP17JoeCP17
8

requesting-code-review

Dispatch a code-reviewer subagent with commit SHA ranges for severity-categorized feedback.

Community
Intermediate
danger-Englishdanger-English
2

requesting-code-review

Dispatch a code-review subagent to analyze git range changes before merging.

Community
Intermediate
FelixBitSoulFelixBitSoul
2

requesting-code-review

Dispatch a code-reviewer agent after task completion for structured Git workflow feedback.

Community
Advanced
ayourtchayourtch

requesting-code-review

Dispatch a code-reviewer subagent to analyze changes against requirements.

Community
Basic