requesting-code-review_skill

Overview

This skill dispatches a code-reviewer subagent to validate recent changes against the plan or requirements before you proceed. It’s designed to catch issues early, guide remediation, and ensure readiness to merge. Use it as a routine gate after tasks, major features, or before merges to main.

How this skill works

You provide commit SHAs (BASE_SHA and HEAD_SHA), a concise description of what was implemented, and the plan or requirements the change should meet. The skill launches the superpowers:code-reviewer subagent, which inspects the diff, tests, and architecture against the supplied plan and returns strengths, categorized issues (Critical/Important/Minor), and an overall assessment. Use the feedback to prioritize fixes: address Critical immediately, resolve Important before proceeding, and track Minor for later.

When to use it

• After each completed task in subagent-driven development
• After finishing a major feature or batch of tasks
• Before merging to main or an integration branch
• When you’re stuck and need a fresh perspective
• Before a large refactor to establish a baseline

Best practices

• Always include BASE_SHA and HEAD_SHA so the reviewer inspects the exact diff
• Supply a clear WHAT_WAS_IMPLEMENTED and PLAN_OR_REQUIREMENTS to focus the review
• Act on Critical issues immediately and Important issues before moving on
• Document or push back with tests and reasoning if you disagree with feedback
• Review early and often to prevent cascading problems

Example use cases

• Just finished Task 2: dispatch review to verify new verification and repair functions
• Before merging a feature branch that implements a new API endpoint
• After completing a three-task batch from an execution plan to confirm readiness
• When a complex bug fix touches core invariants and needs an extra check
• Prior to a large refactor to ensure regressions are caught early