receiving-code-review

Verify code review feedback against codebase constraints before implementation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents performative agreement and blind implementation of code review feedback, ensuring that all changes are technically verified and aligned with the codebase's architectural requirements.

Core Features & Use Cases

  • Verification Protocol: Enforces a strict sequence of reading, understanding, verifying, and evaluating feedback before any implementation occurs.
  • Pushback Framework: Provides structured guidance on when and how to technically challenge incorrect or context-blind suggestions.
  • Use Case: When an external reviewer suggests a refactor that breaks backward compatibility or violates YAGNI principles, this Skill guides the AI to provide a technical counter-argument rather than blindly accepting the change.

Quick Start

Apply the receiving code review protocol to the current pull request feedback by verifying each item against the codebase before proposing any implementation steps.

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, enforce a strict sequence of reading, understanding, and evaluating the suggestion against your codebase before proposing any implementation steps. This ensures all changes are technically sound and tested individually.

What is the best way to handle incorrect code review suggestions?

Handle incorrect code review suggestions by using a structured pushback framework to technically challenge context-blind feedback, providing a technical counter-argument rather than blindly accepting the change.

Why does blindly implementing pull request feedback break software engineering rigor?

Blindly implementing pull request feedback breaks software engineering rigor because it causes performative agreement, bypassing architectural validation and leading to changes that violate existing project constraints or YAGNI principles.

Can I push back on a refactoring suggestion that breaks backward compatibility?

Yes, you can push back on a refactoring suggestion that breaks backward compatibility by applying a technical verification protocol to evaluate the feedback and provide a structured technical counter-argument.

When do I need a verification protocol for code review comments?

You need a verification protocol for code review comments when external or peer feedback requires rigorous architectural validation in software engineering workflows, ensuring all implemented changes are technically sound and compliant.