sp-code-reviewer

Execute a six-phase workflow and generate categorized reports with recommended fixes.

4|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/AlphaComposite/openclaw-superpowers-port --skill sp-code-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sp-code-reviewer
Source: https://github.com/AlphaComposite/openclaw-superpowers-port/tree/main/skills/sp-code-reviewer
Command: npx skills add https://github.com/AlphaComposite/openclaw-superpowers-port --skill sp-code-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires sp-requesting-code-review, sp-subagent-driven-development.

What problem does it solve?

This Skill provides a structured, proactive code-review capability that ensures completed project steps are validated against original plans, quality standards, and architectural goals, reducing miscommunication and rework.

Core Features & Use Cases

  • Six-phase review workflow covering plan alignment, code quality, architecture, documentation, issue categorization, and communication.
  • Standardized output with actionable, prioritized recommendations and clear ownership.
  • Interoperable with sp-requesting-code-review and sp-subagent-driven-development to audit steps after completion.

Quick Start

Prompt the Senior Code Reviewer to evaluate the completed implementation against the original plan.

Frequently Asked Questions about sp-code-reviewer

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

FAQPage Schema
How do I perform a structured code review that aligns completed implementations with original project plans?

A structured code review applies a six-phase workflow to completed implementations, assessing plan alignment, code quality, architecture, and documentation to produce a standardized report with categorized issues and recommended fixes.

What is the best way to automate senior-level code reviews after major project steps?

Senior-level code reviews after major project steps can be structured by enforcing a six-phase workflow that categorizes issues and generates actionable recommendations with clear ownership to reduce miscommunication and rework.

How does issue categorization work during an end-to-end code review?

Issue categorization works through a standardized six-phase review workflow that evaluates code quality, architecture, and documentation, then outputs prioritized recommendations with clear ownership to reduce rework.

Do I need a specific development workflow to use this code review process?

You do not need a specific workflow, but the code review process is interoperable with sp-requesting-code-review and sp-subagent-driven-development to effectively audit completed steps and ensure plan alignment.

Can I use this structured code review to check documentation and architecture quality together?

Yes, you can use this structured code review to check documentation and architecture quality together, as the six-phase workflow explicitly evaluates architectural goals and documentation alongside plan alignment and code quality.