harness:requesting-code-review

Request structured pre-merge code reviews with task-specific reviewer context.

3|1|Updated Apr 5, 2026

Search Tags:#code review #pull request #quality gates #git shas #subagent workflow #pre-merge verification

Ready to run

npx skills add https://github.com/huangbaixun/harness-engineering --skill harness-requesting-code-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: harness:requesting-code-review
Source: https://github.com/huangbaixun/harness-engineering/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/huangbaixun/harness-engineering --skill harness-requesting-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents defects and requirement drift by ensuring work is reviewed before it compounds or merges into the main branch.

Core Features & Use Cases

Dispatch a focused reviewer subagent: requests review with tightly crafted, task-specific context rather than exposing the reviewer to your full session history.
Review at the right checkpoints: supports mandatory review after each subagent-driven development task, after major feature completion, and before merging to main.
Actionable feedback handling: converts reviewer output into clear next steps—fix critical/important items immediately or before continuing, and push back with technical reasoning when feedback is incorrect.

Quick Start

Ask for a review after you finish a task or major change by stating that you want to request code review for your latest commits, including the base and head SHAs.

Frequently Asked Questions about harness:requesting-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I request a pre-merge code review to catch issues before main integration?▼

To request a pre-merge code review, dispatch a focused reviewer subagent with tightly crafted, task-specific context by stating your intent and providing the base and head git SHAs. This initiates a structured pre-merge verification process.

When should I run a structured code review in a subagent workflow?▼

Request a structured code review after completing subagent-driven development tasks, after major feature work, or before merging to main. Optional checkpoints are also supported when refactoring or when blocked.

How do I verify rigid constraints before opening a pull request?▼

Verify rigid constraints by checking the harness-delta.md file and drafting a PR that includes the correct feature reference. Dispatch is blocked if the acceptance criteria are not satisfied.

How to handle feedback from an automated pull request review?▼

Handle PR review feedback by converting reviewer output into clear next steps. Fix critical or important items immediately, or push back with technical reasoning when the automated feedback is incorrect.

Can I review specific git SHAs without exposing the full session history to the reviewer?▼

Yes, dispatching a focused reviewer subagent allows you to request a review with tightly crafted, task-specific context rather than exposing the reviewer to your full session history.

What happens if acceptance criteria are not met during pre-merge verification?▼

During pre-merge verification, the system blocks dispatch when acceptance criteria are not satisfied, preventing defects and requirement drift from compounding into production or mainline integration.