requesting-code-review

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

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/fred-meng/harness --skill requesting-code-review-fred-meng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/fred-meng/harness/tree/main/.github/skills/requesting-code-review
Command: npx skills add https://github.com/fred-meng/harness --skill requesting-code-review-fred-meng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often get merged without independent review, letting bugs, architecture problems, and unmet requirements slip through. This Skill structures the process of requesting an independent code review from a dedicated reviewer subagent so issues are caught before they cascade. ## Core Features & Use Cases - Structured Review Dispatch: Provides a repeatable workflow for gathering git SHAs and dispatching a code-reviewer subagent with precisely scoped context. - Reusable Reviewer Template: Ships a code-reviewer.md prompt template with placeholders for implementation details, requirements, and commit ranges, plus a severity-based output format (Critical, Important, Minor). - Workflow Integration Guidance: Defines when reviews are mandatory (after each task, before merge) and how to act on feedback, including when to push back on incorrect findings. - Use Case: After finishing a feature task, you capture the base and head commit SHAs, dispatch the reviewer subagent with the plan reference, receive a severity-categorized assessment, fix Critical and Important issues, and only then proceed to the next task. ## Quick Start Ask the agent to request a code review of the changes between the current HEAD and the previous commit 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 a code-reviewer subagent using the code-reviewer.md template filled with what was implemented, the requirements, and the commit range. Act on Critical and Important issues before merging.

When should code review be requested during development?

Reviews are mandatory after each task in subagent-driven development, after completing a major feature, and before merging to main. They are also valuable when stuck, before refactoring, or after fixing a complex bug.

What information does a code reviewer subagent need?

The reviewer needs what was implemented, the plan or requirements it should satisfy, the base and head git SHAs defining the diff range, and a brief description. It never receives your session history, keeping the review focused on the work product.

How are code review issues categorized by severity?

Issues are grouped into Critical (bugs, security, data loss), Important (architecture problems, missing features, test gaps), and Minor (style, optimizations). Each issue includes a file:line reference, why it matters, and how to fix it.

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 reviewer's concern.