skills.rest
rinbarpen
rinbarpenCOMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

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

Updated Jan 12, 2025
Search Tags:#code quality#git#workflow#code review#merge#diff#subagent
One-click install
npx skills add https://github.com/rinbarpen/NeuroTrain --skill requesting-code-review-rinbarpen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/rinbarpen/NeuroTrain/tree/main/.cursor/commands/requesting-code-review
Command: npx skills add https://github.com/rinbarpen/NeuroTrain --skill requesting-code-review-rinbarpen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often get merged without systematic review, letting bugs, architectural issues, and unmet requirements slip into production. This Skill standardizes the review request process by dispatching a dedicated code-reviewer subagent with a structured template. ## Core Features & Use Cases - Structured Review Dispatch: Collects git SHAs and fills a review template with implementation details, requirements, and commit range. - Severity-Categorized Feedback: The reviewer returns issues classified as Critical, Important, or Minor with file:line references and a merge readiness verdict. - Workflow Integration: Fits subagent-driven development, plan execution, and ad-hoc development, with mandatory reviews after tasks and before merges. - Use Case: After completing a feature task, run this Skill to have a reviewer subagent diff your commits against the plan, flag a missing progress indicator as Important, and confirm the work is ready to proceed. ## Quick Start Ask the assistant to request a code review of the changes just implemented 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 for my changes before merging?▼

Get the base and head git SHAs for your change range, then dispatch the code-reviewer subagent with the filled template describing 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 useful when stuck, before refactoring, or after fixing a complex bug.

What does the code reviewer check in a review?▼

The reviewer checks code quality, architecture, testing, and requirement coverage against the plan. It also assesses production readiness including migrations, backward compatibility, and documentation, then categorizes issues as Critical, Important, or Minor.

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.

Can I skip code review for simple changes?▼

No. The Skill explicitly warns against skipping review because a change seems simple. Reviewing early and often catches issues before they compound across tasks.

Related Skills

Explore More Software Engineering Skills→
ferdiangunawanferdiangunawan
6

plan

Convert validated research into a detailed implementation plan document.

Community
Advanced
gquthiergquthier
14

requesting-code-review

Dispatch a reviewer subagent to validate code changes before merging.

Community
Advanced
thisismynewfmail-uithisismynewfmail-ui

requesting-code-review

Verifies code changes before commit via diff analysis, tests, and linters.

Community
Advanced
robinebersrobinebers
46

shepherd

Automate GitHub pull request review management until human approval.

Community
Advanced