receiving-code-review

Validate code review feedback against the codebase before implementing changes.

1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/xxih/ai-harness-zh --skill receiving-code-review-xxih
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/xxih/ai-harness-zh/tree/main/references/translations/superpowers/skills/receiving-code-review
Command: npx skills add https://github.com/xxih/ai-harness-zh --skill receiving-code-review-xxih

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides agents on how to process code review feedback responsibly, ensuring technical verification before any implementation and avoiding perfunctory agreement.

Core Features & Use Cases

  • Verification First: Reads feedback, checks against the codebase, and validates technical soundness.
  • Clarify Ambiguities: Prompts for clarification when feedback is unclear before proceeding.
  • Technical Pushback: Provides reasoned objections when suggestions conflict with the codebase or are unnecessary (YAGNI).
  • Use Case: When a reviewer suggests changes that may break existing functionality, the skill helps the agent evaluate, ask questions, and implement fixes safely.

Quick Start

Ask the agent to review the latest pull request feedback, verify each comment against the code, and propose a concise response.

Frequently Asked Questions about 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?

To verify code review feedback, read the reviewer comments, check them against the actual codebase, and validate technical soundness before proceeding. This prevents blind acceptance and maintains technical correctness during pull request reviews.

What should I do when code review comments are unclear?

When code review comments are unclear, you should prompt the reviewer for clarification before proceeding with any implementation. This ensures you fully understand the feedback and avoid making incorrect changes to the codebase.

How to push back on unnecessary pull request suggestions using YAGNI?

To push back on unnecessary pull request suggestions using YAGNI, provide reasoned objections when changes conflict with the codebase or are not currently needed. This enforces YAGNI principles and prevents software bloat.

Can I use this approach for any software project's pull request reviews?

Yes, you can use this approach for any software project's pull request reviews. It is designed to assess, clarify, and respond to reviewer comments regardless of the platform, ensuring technical correctness and clear communication across different environments.

Why does an agent blindly accept code review feedback without verification?

An agent blindly accepts code review feedback without verification because it lacks a process to validate technical soundness. Implementing a verification-first approach prevents this perfunctory agreement and ensures suggestions are checked against the codebase.