harness:receiving-code-review

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.