superpowers-code-review

Automate pre-merge code review workflows for Git-based projects.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/susantosanto/config-opencode --skill superpowers-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: superpowers-code-review
Source: https://github.com/susantosanto/config-opencode/tree/main/skills/superpowers-code-review
Command: npx skills add https://github.com/susantosanto/config-opencode --skill superpowers-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Open-code review processes often suffer from inconsistency and delays during pre-merge checks, which can let defects slip into main and slow down releases. This Skill automates a structured pre-merge code review workflow, enforcing standards, collecting reviewer feedback, and accelerating safe merges.

Core Features & Use Cases

  • Automated pre-merge checklists triggered after task completion or feature branch creation.
  • Severity-based feedback flow (Critical, Important, Minor) to clearly guide fixes before merge.
  • Integrates with subagent-driven development workflows to maintain consistent code quality across teams.

Quick Start

Load the superpowers-code-review tool and run a pre-merge checklist on the latest commit.

Frequently Asked Questions about superpowers-code-review

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

FAQPage Schema
How do I automate pre-merge code reviews for Git feature branches?

Automate pre-merge code reviews by applying a structured checklist to feature branches before merging to main. This workflow integrates a reviewer subagent to evaluate code quality and record feedback consistently.

How does a severity-based checklist work in an automated code review?

A severity-based code review checklist categorizes feedback into Critical, Important, and Minor levels. This mechanism clearly guides developers on which fixes are necessary before merging, ensuring defects do not slip into the main branch.

Can I integrate an AI assistant into my subagent-driven development workflow?

You can integrate an AI assistant into subagent-driven development workflows to maintain consistent code quality across teams. The assistant acts as a reviewer subagent, enforcing a structured checklist and recording feedback automatically.

What is the best way to enforce quality assurance before merging to main?

The best way to enforce quality assurance before merging to main is automating a pre-merge code review workflow. This approach applies a severity-based checklist to feature branches after task completion to prevent defects and accelerate safe merges.

When do I need to run an automated pre-merge code review?

Run an automated pre-merge code review after completing a task or creating a feature branch. This timing ensures code quality is evaluated and feedback is recorded before any changes are merged into the main branch.