requesting-code-review

Dispatches a code-reviewer subagent to review git diffs against requirements before merging.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/AarushiShah/coding-agents-databricks-apps --skill requesting-code-review-aarushishah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/AarushiShah/coding-agents-databricks-apps/tree/main/.claude/skills/requesting-code-review
Command: npx skills add https://github.com/AarushiShah/coding-agents-databricks-apps --skill requesting-code-review-aarushishah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often get merged without systematic review, letting bugs, architecture problems, and unmet requirements slip into production. This Skill structures the review process by dispatching a dedicated code-reviewer subagent that compares your implementation against the original plan. ## Core Features & Use Cases - Automated Review Dispatch: Captures base and head git SHAs, fills a structured review template, and dispatches a superpowers:code-reviewer subagent. - Severity-Categorized Feedback: Returns issues classified as Critical, Important, or Minor with file:line references and a clear merge verdict. - Workflow Integration: Supports review after each task in subagent-driven development, after batches in plan execution, or before merging ad-hoc work. - Use Case: After completing a feature task, run the review to catch missing error handling or test gaps before proceeding to the next task, preventing issues from compounding. ## Quick Start Ask the agent to request a code review of the changes you just completed before moving on to the next task.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I request a code review before merging changes?

Get the base and head git SHAs with git rev-parse, then dispatch the code-reviewer subagent with a description of what was implemented and the requirements. The reviewer returns categorized issues and a merge readiness verdict.

When should I request a code review during development?

Request review after each task in subagent-driven development, after completing a major feature, and before merging to main. It is also valuable when stuck, before refactoring, or after fixing a complex bug.

What does the code reviewer check in a git diff?

The reviewer checks code quality, architecture, testing, and requirement coverage against the plan. It also assesses production readiness including migrations, backward compatibility, and documentation.

How are code review issues categorized by severity?

Issues are classified as Critical (bugs, security, data loss), Important (architecture problems, missing features, test gaps), or Minor (style, optimizations). Each issue includes a file:line reference and an explanation of why it matters.

What should I do if I disagree with the code review feedback?

Push back with technical reasoning and show code or tests that prove the implementation works. You can request clarification, but never ignore Critical issues or proceed with unfixed Important issues.