skills.rest
DNepovim
DNepovimCOMMUNITY
Explore all skills by this author →
Website𝕏@DNepovimGitHub

requesting-code-review

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

Updated Dec 19, 2024
Search Tags:#quality assurance#code review#subagent#merge readiness#git diff#severity
One-click install
npx skills add https://github.com/DNepovim/yadm --skill requesting-code-review-dnepovim
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/DNepovim/yadm/tree/main/.claude/plugins/cache/claude-plugins-official/superpowers/5.0.6/skills/requesting-code-review
Command: npx skills add https://github.com/DNepovim/yadm --skill requesting-code-review-dnepovim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often get merged without independent review, letting bugs, architecture flaws, and unmet requirements slip through. This Skill structures the process of requesting an objective code review from a dedicated subagent so issues are caught before they cascade. ## Core Features & Use Cases - Subagent-Based Review: Dispatches a superpowers:code-reviewer subagent with a precisely crafted prompt template, keeping the reviewer focused on the work product rather than your session history. - Severity-Categorized Feedback: Returns issues classified as Critical, Important, or Minor with file:line references, plus a clear merge-readiness verdict. - Use Case: After completing a task in subagent-driven development, capture the base and head git SHAs, dispatch the reviewer with the implementation summary and plan reference, then fix Critical and Important issues before proceeding to the next task. ## Quick Start Ask the AI to request a code review of the changes between the previous commit and HEAD using the code-reviewer template before merging.

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?▼

Get the base and head commit SHAs with git rev-parse, then dispatch the code-reviewer subagent with what was implemented, the plan reference, and the SHA range. 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, documentation, and obvious bugs.

How are code review issues categorized by severity?▼

Issues are split into Critical (bugs, security, data loss), Important (architecture problems, missing features, test gaps), and Minor (style, optimizations). Each issue includes a file:line reference, why it matters, and how to fix it.

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

Push back with technical reasoning rather than ignoring the feedback. Show code or tests that prove the implementation works, and request clarification from the reviewer if the concern is unclear.

Related Skills

Explore More Software Engineering Skills→
Chikage0o0Chikage0o0
34

requesting-code-review

Request code reviews for committed Git ranges using the OpenCode task tool.

Community
Intermediate
cslsoftwarescslsoftwares

quality-hotfix-workflow

Orchestrate production hotfix workflows from branch creation to patch release.

Community
Advanced
dimetrondimetron
122

code-review-pi

Orchestrate Go code quality review with linters, tests, and coverage.

Community
Advanced
AAbdulghanyAAbdulghany

code-review

Automate pull request reviews with role-based gating and human sign-off.

Community
Advanced