receiving-code-review

Evaluate code-review feedback against the codebase before implementing changes.

9|2|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/DmitriyPolukhin/antigravity-superpower --skill receiving-code-review-dmitriypolukhin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/DmitriyPolukhin/antigravity-superpower/tree/main/modules/receiving-code-review
Command: npx skills add https://github.com/DmitriyPolukhin/antigravity-superpower --skill receiving-code-review-dmitriypolukhin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents confusing, unclear, or questionable code-review feedback from being followed blindly, reducing regressions and wasted engineering time by enforcing verification before changes.

Core Features & Use Cases

  • Structured review reception: Read feedback fully, restate requirements, verify against the real codebase, and evaluate whether the suggestion is technically correct.
  • Guardrails against performative behavior: Avoid empty agreement and gratitude; respond with technical acknowledgment or reasoned pushback instead.
  • Unclear-item handling: Stops implementation when any items are unclear and requests clarification to avoid partial or incorrect changes.
  • Safe implementation workflow: Implements multi-item feedback one item at a time with testing and regression checks, prioritizing blocking issues first.
  • Context-aware YAGNI validation: Greps for actual usage to decide whether “properly implement” suggestions are needed or should be removed as unused.

Quick Start

Use the receiving-code-review skill when you receive code-review feedback that may be unclear or technically questionable so the agent verifies the request against the codebase and tests changes one-by-one.

Frequently Asked Questions about receiving-code-review

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

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

To handle ambiguous code review feedback, you should fully read the comments, restate the requirements, and verify the suggestions against the actual codebase before making any changes to prevent regressions.

What is the best way to push back on technically incorrect code review comments?

The best way to push back on incorrect code review comments is to verify the assumption against the codebase and respond with technical reasoning instead of empty agreement or performative gratitude, ensuring the discussion remains objective.

How do I implement multi-item code review requests safely without breaking existing tests?

To implement multi-item code review requests safely, address each item one at a time, prioritizing blocking issues first, and run testing and regression checks after each change to ensure codebase stability throughout the process.

When should I request clarification on code review feedback instead of implementing it?

You should request clarification on code review feedback whenever any items are unclear, have ambiguous scope, or contain potentially incorrect technical assumptions, stopping implementation entirely until all unclear points are resolved.

How do I validate YAGNI suggestions during a code review?

To validate YAGNI suggestions during a code review, grep the codebase for actual usage of the feature in question to decide whether the requested implementation is necessary or should be removed as unused code.