skills.rest
marcocpt
marcocptCOMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

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

Updated Jun 11, 2026
Search Tags:#git#quality assurance#code review#development workflow#subagent#merge validation#severity triage
One-click install
npx skills add https://github.com/marcocpt/trae_skills --skill requesting-code-review-marcocpt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/marcocpt/trae_skills/tree/main/requesting-code-review
Command: npx skills add https://github.com/marcocpt/trae_skills --skill requesting-code-review-marcocpt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It catches bugs, architecture flaws, and requirement gaps early by having a dedicated reviewer subagent examine your completed work before issues compound or code reaches main. ## Core Features & Use Cases - Structured Review Dispatch: Sends a code-reviewer subagent a curated context (what was implemented, requirements, git SHA range) instead of your full conversation history. - Severity-Triaged Feedback: Returns findings classified as Critical, Important, or Minor with file:line references and fix guidance. - Workflow Integration: Fits subagent-driven development (review after each task), plan execution (review every batch), and ad-hoc work (review before merging). - Use Case: After finishing a feature task, you capture the base and head git SHAs, dispatch the reviewer with the plan reference, receive an assessment like "mergeable after fixes", address the Important issues, and continue to the next task. ## Quick Start Ask the AI to request a code review of your just-completed task using the git range from the previous commit to HEAD before continuing.

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

Capture the base and head git SHAs with git rev-parse, then dispatch a code-reviewer subagent using the provided template. Fill in what was implemented, the plan reference, and the SHA range so the reviewer examines only the relevant diff.

When should I request a code review during development?▼

Request a review after each completed task in subagent-driven development, after finishing significant features, and before merging to main. Reviews are also valuable when stuck, before refactoring, or after fixing complex bugs.

How are code review findings classified by severity?▼

Findings are classified as Critical (bugs, security issues, data loss risks), Important (architecture problems, missing features, test gaps), or Minor (style, optimizations). Each issue includes a file:line reference, explanation, and fix guidance.

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

Push back with technical reasoning rather than accepting incorrect feedback. Show working code or tests that prove your approach, and ask for clarification on the reviewer's concern.

Can I skip code review for simple changes?▼

No, the skill explicitly prohibits skipping reviews because a change seems simple. Early and frequent review catches issues before they compound, and even small changes can introduce subtle bugs.

Related Skills

Explore More Software Engineering Skills→
octanutri-clinoctanutri-clin

requesting-code-review

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

Community
Intermediate
gquthiergquthier
14

requesting-code-review

Dispatch a reviewer subagent to validate code changes before merging.

Community
Advanced
DataDogDataDog
648

lint

Run Hatch-based lint, format, and quality checks on modified files.

Official
Advanced
luiztrilhaluiztrilha

requesting-code-review

Dispatch a code-reviewer subagent for specified git commits.

Community
Advanced