What it does
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Skills ZICQ category:Agent Workflows requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Official URL:GitHub
Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
completing tasks, implementing major features, or before merging to verify work meets requirements
Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Requesting Code Review; When to Request Review; How to Request; Example; Common Rationalizations; Red Flags. It includes spec-recommended sections: input/output examples.
File analysis: instruction-only skill (SKILL.md). The agent loads the full body when activated.
Requesting Code ReviewWhen to Request ReviewHow to RequestExampleCommon RationalizationsRed Flags
Source category:GitHub skill skills.sh agent-skill
namerequesting-code-reviewdescriptionInvocation syntax and available tools depend on your Agent client. Client integration guide ↗
Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.
Copy these instructions to a compatible agent and confirm the target directory matches your client.
Install the agent skill "requesting-code-review" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-a1ff198cd8d5f393-Requesting-Code-Review.html Save it as .cursor/skills/requesting-code-review/SKILL.md or .claude/skills/requesting-code-review/SKILL.md and keep the frontmatter name and description exactly as-is.
Requires Node.js and npx. First inspect the repository's skill list to confirm the name.
npx skills add 'https://github.com/obra/superpowers/tree/HEAD/skills/requesting-code-review' --list
npx skills add 'https://github.com/obra/superpowers/tree/HEAD/skills/requesting-code-review' --skill 'requesting-code-review'
The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.
Dispatch a code reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation — never your session's history.
Core principle: Review early, review often.
Mandatory:
Optional but valuable:
1. Get git SHAs:
BASE_SHA=$(git rev-parse HEAD~1) # or origin/main
HEAD_SHA=$(git rev-parse HEAD)
2. Dispatch code reviewer subagent:
Dispatch a general-purpose subagent, filling the template at code-reviewer.md
Placeholders:
{DESCRIPTION} - Brief summary of what you built{PLAN_OR_REQUIREMENTS} - What it should do{BASE_SHA} - Starting commit{HEAD_SHA} - Ending commit3. Act on feedback:
[Just completed Task 2: Add verification function]
You: Let me request code review before proceeding.
BASE_SHA=$(git log --oneline | grep "Task 1" | head -1 | awk '{print $1}')
HEAD_SHA=$(git rev-parse HEAD)
[Dispatch code reviewer subagent]
DESCRIPTION: Added verifyIndex() and repairIndex() with 4 issue types
PLAN_OR_REQUIREMENTS: Task 2 from docs/superpowers/plans/deployment-plan.md
BASE_SHA: a7981ec
HEAD_SHA: 3df7661
[Subagent returns]:
Strengths: Clean architecture, real tests
Issues:
Important: Missing progress indicators
Minor: Magic number (100) for reporting interval
Assessment: Ready to proceed
You: [Fix progress indicators]
[Continue to Task 3]
| Excuse | Reality | |--------|---------| | "I'll just review the diff myself instead of dispatching a reviewer" | You're the coordinator — reviewing the diff inline burns the context window you need to keep driving the work. Dispatch a reviewer subagent: the diff and the evaluation live in its context, and only the findings come back to you. | | "The reviewer needs my whole session history to understand the change" | Hand it precisely crafted context, never your session's history. That keeps the reviewer on the work product, not your thought process. |
Never:
If reviewer wrong:
See template at: code-reviewer.md
Agent Workflows
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that exte…
Agent Workflows
Use the ClawdHub CLI to search, install, update, and publish agent skills from clawdhub.com. Use when you need to fetch new skills on the fl…
Agent Workflows
Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team …
Agent Workflows
Spec-first, TDD, subagent-driven software development workflow. Use when: (1) building any new feature or app — triggers brainstorm → plan →…