sp-requesting-code-review

Name: sp-requesting-code-review
Availability: InStock
Author: alphacomposite

Dispatch a code-reviewer session to review changes before merging.

4|Updated Feb 27, 2026

Search Tags:#workflow #review #code-quality #quality-assurance #code-review #pull-request #sessions_spawn

Ready to run

npx skills add https://github.com/AlphaComposite/openclaw-superpowers-port --skill sp-requesting-code-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sp-requesting-code-review
Source: https://github.com/AlphaComposite/openclaw-superpowers-port/tree/main/skills/sp-requesting-code-review
Command: npx skills add https://github.com/AlphaComposite/openclaw-superpowers-port --skill sp-requesting-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures early detection of issues by routing a dedicated code-review session to evaluate new changes before merging.

Core Features & Use Cases

Spawn a code-reviewer session using the code-reviewer prompt template located at code-reviewer.md.
Fill in the WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION to drive focused feedback.
Act on the reviewer feedback to resolve critical issues quickly and document decisions for audit trails.

Quick Start

Spawn a code-reviewer session for your latest changes by running sessions_spawn with the code-reviewer prompt, supplying WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION.

Frequently Asked Questions about sp-requesting-code-review

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

FAQPage Schema

How do I automate a pre-merge code review for a pull request?▼

To automate a pre-merge code review, spawn a reviewer session using the sessions_spawn function with a code-reviewer prompt template. This dispatches a focused session to evaluate new pull request changes before merging.

What inputs do I need to provide to spawn a code-reviewer session?▼

Spawning a code-reviewer session requires explicit inputs: WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION. These parameters drive focused feedback by giving the reviewer context about the changes.

When should I use an automated code review session instead of manual review?▼

Use an automated code review session during subagent-driven development workflows or for major feature commits. Dispatching a dedicated reviewer early ensures prompt defect detection before merging changes into the main branch.

How does a code-reviewer prompt template work with sessions_spawn?▼

The code-reviewer prompt template located at code-reviewer.md is loaded when you run sessions_spawn. It configures the spawned session to evaluate code quality based on the provided implementation details and commit range.

What should I do after receiving feedback from a pre-merge code review?▼

After receiving reviewer feedback, act on it to resolve critical issues quickly and document decisions for audit trails. This ensures code quality issues are fixed before the changes are merged.