skills.rest
prime-radiant-inc
prime-radiant-incOFFICIAL
Explore all skills by this author →
WebsiteGitHub

requesting-code-review

Dispatch a code-reviewer subagent to assess changes and surface feedback.

91|4|Updated Feb 10, 2026
Search Tags:#automation#workflow#documentation#subagent#quality-assurance#code-review
One-click install
npx skills add https://github.com/prime-radiant-inc/serf --skill requesting-code-review-prime-radiant-inc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/prime-radiant-inc/serf/tree/main/agent/skills/requesting-code-review
Command: npx skills add https://github.com/prime-radiant-inc/serf --skill requesting-code-review-prime-radiant-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the initiation of code reviews by dispatching a reviewer subagent to assess changes and surface issues before merges.

Core Features & Use Cases

  • Dispatch the code-reviewer subagent after completing a task to obtain a formal review.
  • Use the templates in code-reviewer.md to structure feedback, including what was implemented, plan/requirements, and the HEAD/BASE commits.
  • Categorize issues by severity and drive timely fixes before proceeding with merging.

Quick Start

Dispatch the code-reviewer subagent after completing a task to obtain a formal review and apply the feedback.

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 review feedback before merging changes to main?▼

Automate code review by dispatching a reviewer subagent to assess changes and surface actionable feedback before merging to main. The workflow structures feedback using templates to categorize issues by severity and drive timely fixes.

What inputs are required to run an automated code review workflow?▼

Required inputs for the code review workflow include BASE_SHA, HEAD_SHA, WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, and DESCRIPTION. These parameters provide the context needed to evaluate changes accurately.

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

Initiate a code review after completing tasks in subagent-driven development, after major features, or before merging to main. This timing catches issues early and provides fresh perspective on recent changes.

How does the code review subagent structure its feedback on recent commits?▼

The subagent structures feedback using code-reviewer.md templates, categorizing issues by severity based on the provided HEAD and BASE commits, implementation details, and plan requirements to drive timely fixes.

Can I use this automated code review workflow without any external dependencies?▼

Yes, the workflow operates without external dependencies, relying solely on dispatched subagents and structured templates to assess changes and surface issues before merges.

Related Skills

Explore More Software Engineering Skills→
seanGSISGseanGSISG
3

requesting-code-review

Dispatch a code-reviewer subagent with Git SHAs and implementation details.

Community
Basic
peancharoenpeancharoen

speckit.reviewer

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

Community
Intermediate
uv-xiaouv-xiao
1

uv-subagent-driven-development

Orchestrate subagent-driven development workflows for implementation plans in git worktrees.

Community
Advanced
AetherCore-DevAetherCore-Dev
9

requesting-code-review

Dispatch a code-reviewer subagent to analyze Git changes between commit SHAs.

Official
Intermediate