spurpower-requesting-code-review

Dispatch a reviewer subagent to standardize code review workflows.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/getspur/spur --skill spurpower-requesting-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spurpower-requesting-code-review
Source: https://github.com/getspur/spur/tree/main/.claude/skills/spurpower-requesting-code-review
Command: npx skills add https://github.com/getspur/spur --skill spurpower-requesting-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the lack of rigorous quality control in subagent-driven development by providing a structured, repeatable process for requesting and acting on code reviews before merging changes.

Core Features & Use Cases

  • Context-Aware Reviewing: Dispatches a dedicated code-reviewer subagent with specific implementation details and commit SHAs, ensuring the reviewer focuses on the work product rather than session history.
  • Standardized Review Lifecycle: Enforces mandatory review points after task completion, major feature implementation, and before merging to main.
  • Feedback Integration: Provides a clear protocol for categorizing feedback into critical, important, and minor issues to ensure high-quality code integration.

Quick Start

Use the spurpower-requesting-code-review skill to initiate a formal review of your current changes by providing the base commit, head commit, and a summary of the implemented features.

Frequently Asked Questions about spurpower-requesting-code-review

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

FAQPage Schema
How do I automate code reviews for multi-agent development workflows?

Automate code reviews for multi-agent workflows by dispatching a dedicated reviewer subagent with specific git commit SHAs and requirement documentation, ensuring the reviewer evaluates the work product independently rather than relying on session history.

What is the best way to standardize pre-merge code review in agentic workflows?

Standardize pre-merge code review by enforcing mandatory review checkpoints after task completion, major feature implementations, and before merging to main, using a structured subagent dispatch process to maintain quality assurance.

How does subagent code review handle feedback integration?

Subagent code review handles feedback integration by providing a clear protocol that categorizes review feedback into critical, important, and minor issues, ensuring structured and high-quality code integration before changes are merged.

What do I need to provide to request a code review from a subagent?

To request a code review from a subagent, you need to provide the base git commit SHA, the head commit SHA, and a clear summary of the implemented features or requirement documentation to ensure accurate technical assessment.

When should I trigger a code review subagent in my development cycle?

Trigger a code review subagent at standardized lifecycle points: immediately after task completion, following a major feature implementation, and as a final verification step before merging changes into the main branch.

Why use a dedicated subagent for code review instead of reviewing in the main agent session?

Use a dedicated subagent for code review to ensure context-aware reviewing that focuses strictly on the work product and commit changes, preventing contamination from session history and enforcing rigorous quality control.