receiving-code-review

Triage and respond to code review feedback with verification and prioritized fixes.

19|2|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/bonnguyenitc/antigravity-superpowers --skill receiving-code-review-bonnguyenitc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/bonnguyenitc/antigravity-superpowers/tree/main/.agent/skills/receiving-code-review
Command: npx skills add https://github.com/bonnguyenitc/antigravity-superpowers --skill receiving-code-review-bonnguyenitc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Help developers process and respond to code review feedback in a way that prioritizes technical correctness over performative agreement, prevents blind implementation, and avoids regressions caused by misunderstood or incorrect suggestions.

Core Features & Use Cases

  • Structured Response Pattern: Read full feedback, restate requirements, verify against the codebase, evaluate technical correctness, acknowledge or push back, then implement and test each item.
  • Source-Aware Handling: Differentiate between trusted human partners and external reviewers, applying extra verification for external suggestions and stopping to consult the human partner on conflicts.
  • Risk-Based Implementation Order: Clarify unclear items first, then fix blocking/security issues, simple fixes, and finally complex refactors, testing each change to avoid regressions.
  • Use Case: When a PR receives a mixed set of inline comments from maintainers and external reviewers, use this Skill to triage, verify, and respond with technical acknowledgments or reasoned pushback rather than performing immediate changes.

Quick Start

Restate unclear review items, verify each suggestion against the codebase and tests, ask for clarification when needed, and implement fixes one at a time ordered by severity while providing concise technical acknowledgments or reasoned pushback.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I respond to code review feedback without blindly implementing every suggestion?

To avoid blind implementation of code review feedback, verify each suggestion against the codebase and tests first. Provide concise technical acknowledgments or reasoned pushback rather than performing immediate changes to ensure technical correctness.

How should I prioritize fixes when a PR receives mixed inline comments from multiple reviewers?

When prioritizing PR comments, clarify unclear items first, then fix blocking or security issues, apply simple fixes, and finally execute complex refactors. Test each change individually to avoid regressions while processing the mixed review feedback.

When should I push back on a code review suggestion from an external reviewer?

Push back on external code review suggestions when verifying them against the codebase reveals technical inaccuracies. Apply extra verification to external suggestions and consult your trusted human partner when conflicts arise.

What is the best way to manage GitHub PR review threads to prevent regressions?

The best way to manage GitHub PR review threads is to read full feedback, restate requirements, verify against the codebase, and implement fixes one at a time ordered by severity. Testing each change individually prevents regressions caused by incorrect suggestions.

Does this approach to code review work for external reviewer suggestions on GitHub?

Yes, this code review approach works for external reviewer suggestions on GitHub by applying source-aware handling. It differentiates between trusted human partners and external reviewers, requiring extra verification and consultation when conflicts occur.