receiving-code-review

Process code-review feedback through a structured verify-and-implement workflow.

437|13|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/derHaken/SuperAntigravity --skill receiving-code-review-derhaken
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/derHaken/SuperAntigravity/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/derHaken/SuperAntigravity --skill receiving-code-review-derhaken

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code-review feedback often blends technical critique with social dynamics, leading to unclear requirements or rushed, potentially unsafe implementations. This Skill provides a disciplined workflow to receive feedback, verify it against the codebase, and push back with technical reasoning before acting.

Core Features & Use Cases

  • Structured feedback processing: read, understand, verify, evaluate, respond, and implement in safe, incremental steps.
  • Safety and correctness: prevents performative agreement and ensures changes align with project constraints and tests.
  • Use Cases: when feedback is unclear, conflicting, or requires justification from external reviews before changes are made.

Quick Start

Start by restating each feedback item in your own words, verify it against the codebase, and implement changes one item at a time after confirming technical correctness.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I process code-review feedback without blindly implementing changes?

Process code-review feedback by applying a structured workflow: read, understand, verify against the codebase, evaluate, respond, and implement. This prevents performative agreement and ensures technical rigor before modifying code.

What is the best way to handle conflicting or unclear pull-request feedback?

Handle unclear pull-request feedback by restating the critique in your own words, verifying the technical claims against the codebase, and pushing back with technical reasoning before making any unsafe code modifications.

When do I need a structured response pattern for receiving code reviews?

A structured response pattern for code reviews is needed when feedback is unclear, conflicting, or requires technical justification from external reviewers before executing changes to ensure project constraints and tests are met.

How do I verify code-review feedback before implementing suggested changes?

Verify code-review feedback by evaluating the suggested changes against the existing codebase, ensuring they align with project constraints, and confirming technical correctness through testing before incremental implementation.

Can I use this structured feedback workflow for external code reviews?

Yes, this structured feedback workflow applies to both internal and external code reviews, ensuring verification and testing are essential when justifying changes from outside contributors before implementation.

Why should I push back on code-review feedback instead of immediately coding it?

Pushing back on code-review feedback enforces safety and correctness, preventing rushed or potentially unsafe implementations by requiring technical reasoning and verification before acting on the critique.