requesting-code-review_skill

This skill helps you request timely code reviews to catch issues early, ensure requirements are met, and guide fixes before merging.

Shell

36.9k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill obra/superpowers --skill requesting-code-review

code-reviewer.md3.3 KB
SKILL.md2.6 KB

Overview

This skill helps developers request targeted code reviews using a dedicated code-reviewer subagent to catch issues early and keep work aligned with requirements. It formalizes when to request reviews, how to provide context, and how to act on feedback so tasks move forward with minimal rework.

How this skill works

You capture the git range (BASE_SHA and HEAD_SHA), fill a short template describing what was implemented and the plan or requirements, and dispatch the superpowers:code-reviewer subagent via the Task tool. The subagent inspects the commit diff, tests, and architecture notes, then returns strengths, categorized issues (Critical/Important/Minor), and an assessment.

When to use it

After completing each task in subagent-driven development
After finishing a major feature or batch of tasks
Before merging changes into main
When stuck or unsure and you need a fresh perspective
Before large refactors to establish a baseline
After fixing a complex bug

Best practices

Always include BASE_SHA, HEAD_SHA, WHAT_WAS_IMPLEMENTED, and PLAN_OR_REQUIREMENTS in the request
Review early and often—prefer small, focused reviews over large diffs
Act on Critical and Important findings before proceeding; note Minor issues for future work
Provide tests or reproduction steps when pushing back on feedback
Use reviews as learning opportunities; incorporate reviewer strengths into future work

Example use cases

Completed Task 4: add authentication middleware—request review before Task 5
Finished a multi-file refactor—request review to ensure behavior parity before merge
Fixed a production bug—request a quick review to confirm no regression
Working on a planned feature batch—request review after the batch to validate overall design
Stalled on a tricky bug—request review to get an external perspective and potential fixes

FAQ

Use BASE_SHA as the commit or branch head you started from (e.g., origin/main) and HEAD_SHA as your current commit. For small tasks, HEAD~1 and HEAD often suffice.

How should I respond to reviewer disagreements?

Push back with technical reasoning, tests, or examples that demonstrate correctness, and request clarification if feedback is ambiguous.