Engineering
requesting-code-review avatar

requesting-code-review

Enforces code quality by dispatching a dedicated subagent to review work against project plans, requirements, and git commit history before tasks are completed or merged.

Introduction

The requesting-code-review skill acts as a critical quality gate within the Superpowers development methodology. It is designed for software engineers and coding agents who follow an iterative, task-based workflow. By utilizing a detached subagent (superpowers:code-reviewer) to evaluate work, this skill ensures that code changes are scrutinized against predefined plans and requirements without the reviewer being biased by the main session's chat history. This mechanism facilitates a clean, objective assessment of code quality, architecture, and compliance with the intended design.

  • Dispatches the superpowers:code-reviewer subagent to analyze git diffs between specific SHAs.

  • Categorizes feedback into Critical, Important, and Minor issues to prioritize remediation.

  • Enforces strict review requirements after every subagent-driven task, major feature implementation, and before any merge to main.

  • Supports optional review triggers for refactoring, complex bug fixes, or when the agent is stuck.

  • Prevents development from proceeding until all Critical and Important issues are addressed.

  • Preserves the core session's context by offloading the evaluation process.

  • Users should provide clear context including what was implemented, the original plan, and the git hash range (BASE_SHA and HEAD_SHA).

  • The reviewer focuses strictly on the work product; ensure all tests and docs are prepared before initiating.

  • When the reviewer flags an issue, address it immediately. If the feedback is disputed, provide technical reasoning, tests, or code proof to justify the existing implementation.

  • This skill is highly effective when used alongside test-driven development (TDD) as it verifies both implementation and verification steps.

  • Typical constraints include the necessity of a git-based repository and the presence of a formal implementation plan document. It is not intended for trivial "simple" changes that skip quality validation. Always prioritize technical debt management and proactive bug prevention through these early review cycles.

Repository Stats

Stars
171,935
Forks
15,167
Open Issues
278
Language
Shell
Default Branch
main
Sync Status
Idle
Last Synced
Apr 29, 2026, 06:05 AM
View on GitHub