skills.rest
svssdeva
svssdevaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

requesting-code-review

Dispatch a code reviewer subagent using base and head git SHAs.

1|1|Updated Apr 20, 2026
Search Tags:#quality assurance#code review#subagent#requirements validation#git sha#workflow guardrails#merge checks
One-click install
npx skills add https://github.com/svssdeva/agentic-skills --skill requesting-code-review-svssdeva
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/svssdeva/agentic-skills/tree/main/engineering/requesting-code-review
Command: npx skills add https://github.com/svssdeva/agentic-skills --skill requesting-code-review-svssdeva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents bugs and requirement mismatches from slipping into completed work by ensuring a structured review happens before merging or continuing.

Core Features & Use Cases

  • When to request review: Mandates reviews after each subagent-driven task and before merge, with optional reviews when stuck or after refactors.
  • How to request review: Uses git SHAs to provide a reviewer with precisely scoped context for evaluation, avoiding reliance on the current session history.
  • How to act on feedback: Prioritizes fixing Critical and Important issues immediately, records Minor issues for later, and includes a process for pushing back with technical justification.

Quick Start

Use the requesting-code-review skill to dispatch a code reviewer subagent for the changes between your base and head git SHAs, then fix Critical and Important findings before moving forward.

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 against specific git SHAs?▼

To request a code review, dispatch a code reviewer subagent with the base and head git SHAs to scope the evaluation precisely, avoiding reliance on current session history.

When should I trigger a pre-merge code review during development?▼

A pre-merge code review is mandated after each subagent-driven task and before merging to main, with optional reviews recommended when stuck or after refactoring.

What is the workflow for acting on code review feedback?▼

Acting on code review feedback requires fixing Critical and Important issues immediately, recording Minor issues for later, and pushing back with technical justification when necessary.

How does requirements validation work with subagent-driven development?▼

Requirements validation in subagent-driven development works by dispatching a code reviewer subagent early in the lifecycle to ensure completed work is verified against original requirements.

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

Dispatching a code reviewer subagent requires base and head git SHAs for scoped context and a filled code-reviewer.md template to guide the evaluation process.

Related Skills

Explore More Software Engineering Skills→
xotongxotong

requesting-code-review

Dispatch a code-reviewer subagent to evaluate diffs against requirements.

Community
Advanced
indykishindykish
2

review

Analyze branch diffs against origin/main for merge safety issues.

Community
Advanced
kitfunsokitfunso

requesting-code-review

Dispatch a code-review subagent to categorize issues by severity before merging.

Community
Advanced
lv416elv416e
6

requesting-code-review

Dispatch a code-reviewer subagent to review code changes between BASE_SHA and HEAD_SHA.

Community
Basic