skills.rest
MaiconGambini
MaiconGambiniCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

requesting-code-review

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

Updated Jul 29, 2026
Search Tags:#code quality#code review#verification#subagent#git diff#severity#pre-merge
One-click install
npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill requesting-code-review-maicongambini
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/MaiconGambini/opencode-harness-guide/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill requesting-code-review-maicongambini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It catches bugs, architecture flaws, and requirement gaps early by routing completed work through an independent code-reviewer subagent before issues compound or reach the main branch. ## Core Features & Use Cases - Structured Review Dispatch: Fills a code-reviewer template with what was implemented, the plan, and git SHAs so the reviewer evaluates the work product, not your session history. - Severity-Based Feedback: Returns issues categorized as Critical, Important, or Minor with file:line references and a clear merge verdict. - Use Case: After finishing a task in subagent-driven development, capture BASE_SHA and HEAD_SHA, dispatch the reviewer, fix Critical and Important issues, then proceed to the next task with confidence. ## Quick Start Ask the agent 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 the filled template describing what was implemented and the requirements. Act on Critical and Important issues before merging.

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 across the diff between BASE_SHA and HEAD_SHA. It also assesses production readiness including migrations, backward compatibility, and documentation.

What should I do if the code reviewer is wrong?▼

Push back with technical reasoning, showing code or tests that prove the implementation works, and request clarification. Do not ignore valid feedback, but disagreement is acceptable when supported by evidence.

Why does the reviewer not see my session history?▼

The reviewer receives only the crafted template context, keeping it focused on the work product rather than your thought process. This also preserves your own context window for continued work.

Related Skills

Explore More Software Engineering Skills→
fts-profts-pro

requesting-code-review

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

Community
Intermediate
olliecrowolliecrow

git-review

Review a Git branch against main for critical issues and regressions.

Community
Advanced
arndvsarndvs

pr-preflight

Audits changed files, diffs, and stack tooling before opening a pull request.

Community
Advanced
Asygnuz-S-A-SAsygnuz-S-A-S

bmad-checkpoint-preview

Guides human reviewers through code changes via structured walkthrough, risk, and testing steps.

Official
Advanced