skills.rest
epicodic
epicodicCOMMUNITY
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 28, 2026
Search Tags:#code quality#git#code review#development workflow#subagent#merge verification
One-click install
npx skills add https://github.com/epicodic/drift --skill requesting-code-review-epicodic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/epicodic/drift/tree/main/.agents/skills/requesting-code-review
Command: npx skills add https://github.com/epicodic/drift --skill requesting-code-review-epicodic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often get merged without independent verification, letting bugs, architecture flaws, and unmet requirements slip into production. This Skill structures the review request process so every task or feature gets evaluated by a dedicated reviewer with precisely crafted context. ## Core Features & Use Cases - Structured Review Dispatch: Packages the implementation summary, requirements, and git SHA range into a template so the reviewer evaluates the work product, not your session history. - Severity-Triage Feedback: Returns issues categorized as Critical, Important, or Minor with file:line references and a clear merge-readiness verdict. - Use Case: After finishing a task in subagent-driven development, capture the base and head commit SHAs, dispatch the reviewer with the filled template, fix Critical and Important issues, then proceed to the next task with confidence. ## 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 changes?▼

Capture the base and head commit SHAs with git rev-parse, then dispatch the code-reviewer subagent using the provided template. Fill in what was implemented, the requirements, and the SHA range so the reviewer can run git diff and evaluate the changes.

When should I request a code review during development?▼

Request review after each task in subagent-driven development, after completing a major feature, and always before merging to main. It is also valuable when stuck, before refactoring, or after fixing a complex bug.

What does the code review feedback include?▼

The reviewer returns strengths, issues categorized as Critical, Important, or Minor with file:line references, recommendations, a coding-conventions checklist, and a clear verdict on whether the work is ready to merge.

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

Push back with technical reasoning rather than accepting incorrect feedback. Show code or tests that prove the implementation works, and request clarification on the disputed point.

Can I skip code review for simple changes?▼

No. The Skill explicitly warns against skipping review because a change seems simple. Small changes can still introduce bugs or violate conventions, and early review prevents issues from compounding across tasks.

Related Skills

Explore More Software Engineering Skills→
OzeroHAXOzeroHAX
32

docs-project-task

Define implementation tasks with outcomes, boundaries, and validation criteria.

Community
Basic
gquthiergquthier
14

requesting-code-review

Dispatch a reviewer subagent to validate code changes before merging.

Community
Advanced
eygrabereygraber
1

check

Run formatting, detekt, lint, and unit tests on Android and Kotlin projects.

Community
Intermediate
pfangueiropfangueiro
6

code-review-checklist

Generate a code-review checklist covering functionality, design, testing, security, and performance.

Community
Basic