harness:receiving-code-review

Verify code-review feedback for technical correctness and constraint compliance before implementation.

3|1|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/huangbaixun/harness-engineering --skill harness-receiving-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness:receiving-code-review
Source: https://github.com/huangbaixun/harness-engineering/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/huangbaixun/harness-engineering --skill harness-receiving-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents incorrect or unclear code-review suggestions from being implemented blindly by enforcing technical verification, clarification, and safe execution grounded in the codebase and project constraints.

Core Features & Use Cases

  • Verification-first response flow: Restate the requested changes, confirm technical correctness against the actual repository, and only then decide whether to implement.
  • Unclear-feedback handling: Stops implementation when any review item is unclear and requests clarification before taking action.
  • Rigor for external reviewer suggestions: Checks for context fit, regression risk, platform/version compatibility, and whether the reviewer understands full codebase implications.
  • Guardrails for rigid constraints and architecture: Requires features.json reconciliation for rigid-constraint changes and mandates ADR creation/updates for architectural changes before merge.
  • Discourages performative agreement: Avoids gratitude and affirmation-only responses; focuses on concrete technical acknowledgment and verified fixes.

Quick Start

Use this skill when you receive multi-item code-review feedback that is unclear, technically questionable, or potentially risky to implement without validation.

Frequently Asked Questions about harness:receiving-code-review

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

FAQPage Schema
How do I verify code review feedback before implementing changes?

Verify code review feedback by restating the requested changes, confirming technical correctness against the actual repository, and checking for regression risk before deciding to implement.

What should I do when code review feedback is unclear or technically questionable?

When code review feedback is unclear, stop implementation immediately and request clarification from the reviewer before taking any action to avoid implementing incorrect suggestions blindly.

How do I handle code review suggestions that conflict with existing architectural decisions?

Handle conflicting architectural suggestions by mandating ADR creation or updates before merge, ensuring the review feedback undergoes architectural verification rather than silent acceptance or rejection.

How do I ensure regression safety when implementing external reviewer suggestions?

Ensure regression safety with external suggestions by checking context fit, platform compatibility, version constraints, and whether the reviewer understands full codebase implications before implementing.

When do I need to reconcile rigid constraints in features.json during code review?

Reconcile rigid constraints in features.json when code review feedback requests changes that potentially violate rigid project constraints, requiring explicit validation before any implementation proceeds.

How do I avoid performative agreement when responding to code review comments?

Avoid performative agreement by skipping gratitude and affirmation-only responses, focusing instead on concrete technical acknowledgment and verified fixes grounded in the actual codebase.