skills.rest
octanutri-clin
octanutri-clinCOMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

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

Updated Jul 9, 2026
Search Tags:#code quality#code review#pull request#subagent#git diff#merge verification
One-click install
npx skills add https://github.com/octanutri-clin/octaclin --skill requesting-code-review-octanutri-clin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/octanutri-clin/octaclin/tree/main/.agents/skills/requesting-code-review
Command: npx skills add https://github.com/octanutri-clin/octaclin --skill requesting-code-review-octanutri-clin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often ship with undetected bugs, plan deviations, and quality gaps that compound over time. This Skill structures the process of requesting an independent code review so issues are caught early, before they cascade into larger problems. ## Core Features & Use Cases - Subagent Review Dispatch: Fills a reusable reviewer prompt template with a description, requirements, and git SHA range, then dispatches a general-purpose subagent to perform a read-only review. - Severity-Calibrated Feedback: The reviewer returns strengths, issues categorized as Critical, Important, or Minor, recommendations, and a clear merge verdict. - Use Case: After completing a task in subagent-driven development, capture the base and head commit SHAs, dispatch the reviewer with the task plan as requirements, fix any Critical or Important findings, and only then proceed to the next task or merge. ## 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 a general-purpose subagent using the code-reviewer template filled with a description, the requirements, and the SHA range. The reviewer returns categorized issues and a merge 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 useful when stuck, before refactoring, or after fixing a complex bug.

Can the code reviewer subagent modify my working tree?▼

No. The review is strictly read-only on the current checkout. The reviewer uses git show, git diff, and git log, and must use a separate temporary worktree if it needs to inspect another revision.

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

Push back with technical reasoning and show code or tests that prove the implementation works. You can also request clarification rather than accepting invalid feedback.

What feedback format does the code review produce?▼

The reviewer returns strengths, issues grouped as Critical, Important, and Minor with file and line references, recommendations, and a final assessment stating whether the work is ready to merge.

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
p-o-ke-naep-o-ke-nae

github-flow

Guide GitHub Flow branching, commits, testing, pull requests, and squash merges.

Community
Intermediate
roach88roach88
2

jiro-automation-layer

Run linters, type checkers, and test collection workflows for Python, TypeScript, JavaScript, and Nx monorepo projects.

Community
Intermediate
Sir-chawakornSir-chawakorn
33

ai-pair-programming

Facilitate real-time collaborative pair programming sessions between a human developer and an AI.

Community
Intermediate