receiving-code-review

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

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/kgadek/kgadek-claude-plugin --skill receiving-code-review-kgadek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/kgadek/kgadek-claude-plugin/tree/main/ai-spec/2026-01-21-sdd-inspirations/references/obra-superpowers/skills/receiving-code-review
Command: npx skills add https://github.com/kgadek/kgadek-claude-plugin --skill receiving-code-review-kgadek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers avoid performative agreement and blindly implement feedback by enforcing a disciplined, technical workflow for code-review responses.

Core Features & Use Cases

  • Restate requirements to confirm understanding and prevent ambiguity.
  • Verify feedback against the actual codebase and project constraints before implementing changes.
  • Push back with technical reasoning when feedback is unclear, conflicting, or technically questionable.
  • Implement items one at a time with focused testing to minimize regressions.

Quick Start

Read the feedback in full, restate the requirement in your own words, verify it against the codebase, and push back with technical reasoning before implementing changes.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
When should I push back on pull request feedback?

Push back on pull request feedback when comments are unclear, conflicting with existing project constraints, or technically questionable, using technical reasoning to support your response rather than performative agreement.

How do I handle code-review feedback without blindly implementing changes?

Handle code-review feedback by following a disciplined verification workflow: read comments in full, restate requirements to confirm understanding, verify suggestions against the codebase, and push back with technical reasoning before implementing any changes.

What is the best way to respond to unclear code-review comments on a pull request?

The best way to respond to unclear code-review comments is to restate the requirement in your own words and push back with technical reasoning, ensuring ambiguity is resolved before any code changes are implemented.

How does a structured code-review process prevent performative agreement?

A structured code-review process prevents performative agreement by enforcing a six-step pattern—READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT—requiring technical verification against project constraints before agreeing to feedback.

How do I verify technical correctness of code-review feedback before implementing?

Verify technical correctness by checking the feedback against the actual codebase and project constraints, evaluating the technical validity of the suggestion, and implementing items one at a time with focused testing to minimize regressions.

When should I push back on pull request feedback?

Push back on pull request feedback when comments are unclear, conflicting with existing project constraints, or technically questionable, using technical reasoning to support your response rather than performative agreement.