progressive-code-review-gate

Automate progressive code review before commits and pushes.

8|1|Updated Jan 24, 2026

Search Tags:#automation #commit #pre-commit #code-review #gate #progressive #adversarial-review

Ready to run

npx skills add https://github.com/bordenet/superpowers-plus --skill progressive-code-review-gate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: progressive-code-review-gate
Source: https://github.com/bordenet/superpowers-plus/tree/main/skills/engineering/progressive-code-review-gate
Command: npx skills add https://github.com/bordenet/superpowers-plus --skill progressive-code-review-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This gate ensures that every code change undergoes a mandatory progressive review before commit or push, preventing unsafe changes from entering the codebase.

Core Features & Use Cases

Enforces a multi-phase review loop via a sub-agent-reviewer, aggregating feedback and deciding whether to implement, defer, or reject changes.
Integrates into the commit-gates chain and works with enforce-style-guide to respect style rules, enabling automatic re-dispatch on failures.
Use Case: Before pushing a commit, trigger the gate to ensure all defenders (quality, security, design) review changes and provide actionable feedback.

Quick Start

Trigger the progressive code review before committing changes to enforce the mandatory review loop.

Frequently Asked Questions about progressive-code-review-gate

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

FAQPage Schema

How do I enforce a mandatory code review before a git commit?▼

To enforce a mandatory code review before a commit, you need an automated pre-commit gate that blocks unsafe changes. This gate scopes reviews to code changes and maps outcomes to pass or fail verdicts.

What is a progressive code review workflow in CI/CD?▼

A progressive code review workflow in CI/CD is an automated pre-commit process that dispatches multiple reviewers, such as quality and security defenders, to aggregate feedback and decide whether to implement, defer, or reject changes.

How do I automate multi-phase reviewer feedback for code changes?▼

You automate multi-phase reviewer feedback by dispatching a battery of sub-agent reviewers scoped to your code changes. The system aggregates their actionable feedback and triggers re-dispatch on failures to ensure quality.

Does the pre-commit review gate work with style-guide enforcement?▼

Yes, the pre-commit review gate integrates into the commit-gates chain and works directly with style-guide enforcement. This integration enables automatic re-dispatch of reviews when style or quality failures occur.

What are the limitations of automating code review before pushing commits?▼

Automating code review before pushing commits requires strict alignment with pre-commit and style-guide gates. Limitations include potential workflow bottlenecks if the multi-phase review loop triggers frequent re-dispatches on failed changes.