skills.rest
Yvesdefaria
YvesdefariaCOMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

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

Updated Aug 3, 2026
Search Tags:#code quality#quality assurance#code review#merge#subagent#git diff
One-click install
npx skills add https://github.com/Yvesdefaria/GymLab --skill requesting-code-review-yvesdefaria
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/Yvesdefaria/GymLab/tree/main/.opencode/skills/requesting-code-review
Command: npx skills add https://github.com/Yvesdefaria/GymLab --skill requesting-code-review-yvesdefaria

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often get merged without independent review, letting bugs and architectural issues cascade into later work. This Skill structures the process of requesting an objective code review from a subagent with precisely crafted context. ## Core Features & Use Cases - Structured Review Dispatch: Provides a complete prompt template for a code reviewer subagent covering plan alignment, code quality, architecture, testing, and production readiness. - Severity-Calibrated Feedback: The reviewer returns findings categorized as Critical, Important, or Minor, with file:line references and a clear merge verdict. - Use Case: After completing a feature task, you capture the base and head git SHAs, dispatch the reviewer subagent with the template, and receive an assessment of whether the work is ready to merge 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.

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 with an AI subagent?▼

Capture the base and head git SHAs for your change range, then dispatch a general-purpose subagent using the code-reviewer template with a description, requirements, and the SHAs. The reviewer inspects the diff and returns categorized findings.

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.

What does the code reviewer subagent check?▼

The reviewer checks plan alignment, code quality, architecture, testing, and production readiness. It returns strengths, issues categorized as Critical, Important, or Minor with file:line references, recommendations, and a merge readiness verdict.

Can the code reviewer subagent modify my code?▼

No. The review is strictly read-only on the checkout. The reviewer uses git show, git diff, and git log to inspect history and must not mutate the working tree, index, HEAD, or branch state.

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, but never ignore valid Critical or Important issues without addressing them.

Related Skills

Explore More Software Engineering Skills→
robot-dennyrobot-denny

retrofit

Reconciles unreviewed code changes against intent and drafts missing tests, docs, and review findings.

Community
Advanced
olliecrowolliecrow

git-review

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

Community
Advanced
Open-PawsOpen-Paws
3

code-review

Automate layered code review for pull requests in CI pipelines.

Official
Advanced
RisorseArtificialiRisorseArtificiali
9

adversarial-code-review

Reviews branches and pull requests using fresh-context reviewer subagents with execution-based verification.

Official
Advanced