receiving-code-review

Validate code review feedback against the codebase before implementing fixes.

7|3|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/brainbrewlabs/brainbrew-devkit --skill receiving-code-review-brainbrewlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/brainbrewlabs/brainbrew-devkit/tree/main/plugin/config/templates/develop/skills/receiving-code-review
Command: npx skills add https://github.com/brainbrewlabs/brainbrew-devkit --skill receiving-code-review-brainbrewlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents blind or performative acceptance of code review feedback by enforcing verification, technical reasoning, and tested, ordered implementation so that changes do not introduce regressions or unnecessary work.

Core Features & Use Cases

  • Verify before implementing: Restate requirements, grep the codebase, and confirm the suggested change applies.
  • Prioritize and implement safely: Clarify unclear items, handle blocking/security fixes first, implement one item at a time and run tests.
  • Reasoned pushback: Provide technical arguments, ask clarifying questions, and escalate to your human partner when decisions conflict.
  • Use Case: Responding to external reviewer comments on a pull request to avoid breaking compatibility and follow YAGNI rules.

Quick Start

Review the PR comments, restate unclear items, verify against the codebase, and implement one tested fix at a time.

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, restate the requirements, grep the codebase to confirm the suggested change applies, and evaluate the technical risks. This prevents blind or performative acceptance of pull request comments and avoids introducing regressions.

What is the best way to prioritize and implement pull request review comments?

Prioritizing pull request review comments involves clarifying unclear items, handling blocking and security fixes first, and implementing one item at a time. Run tests after each single-item implementation to ensure verified, safe changes.

How do I push back on incorrect code review suggestions?

To push back on incorrect code review suggestions, provide technical arguments against the feedback, ask clarifying questions, and escalate to your human partner when decisions conflict. This ensures reasoned pushback instead of blind implementation.

When should I apply YAGNI rules to external reviewer comments on a pull request?

Apply YAGNI rules to external reviewer comments when suggestions introduce unnecessary work or break compatibility. Verify the feedback against the codebase first to ensure the requested changes satisfy actual requirements without adding unneeded functionality.

Can I use this process for any type of team feedback and technical verification?

Yes, this process applies to pull request reviews, external reviewer comments, and team feedback where technical verification, scope clarification, and risk evaluation are required to prevent incorrect implementations and regressions.