receiving-code-review

Standardize evaluation of incoming code review feedback against codebase constraints.

1|Updated Mar 15, 2026

Search Tags:#software engineering #code review #pull request #refactoring #verification #technical rigor

Ready to run

npx skills add https://github.com/Luizfbm/Dev-roast --skill receiving-code-review-luizfbm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/Luizfbm/Dev-roast/tree/main/.agents/skills/receiving-code-review
Command: npx skills add https://github.com/Luizfbm/Dev-roast --skill receiving-code-review-luizfbm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates performative agreement and blind implementation during code reviews, ensuring that feedback is technically verified against the codebase before any changes are made.

Core Features & Use Cases

Technical Verification Protocol: Forces a structured approach to evaluate feedback for technical correctness and context-awareness.
Pushback Framework: Provides clear, non-defensive methods to challenge incorrect or context-blind suggestions.
Use Case: When a reviewer suggests a refactor that breaks existing legacy compatibility or violates YAGNI principles, this skill guides you to verify the codebase and push back with technical evidence rather than accepting the suggestion blindly.

Quick Start

Use the receiving-code-review skill to analyze the latest pull request feedback and determine which items require verification before implementation.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema

How do I handle pull request feedback that breaks existing codebase compatibility?▼

To handle pull request feedback that risks breaking legacy compatibility, verify the suggestion against existing codebase constraints before implementing changes. Apply a technical verification protocol to evaluate architectural alignment and push back with evidence if the refactor violates project requirements.

What is the best way to push back on incorrect code review suggestions?▼

The best way to push back on incorrect code review suggestions is using a non-defensive framework that challenges context-blind feedback with technical evidence. Verify the codebase impact first, then communicate the architectural constraints or YAGNI principle violations clearly.

How do I stop blindly accepting code review comments and verify technical accuracy?▼

Stop blindly accepting code review comments by applying a strict technical verification protocol to evaluate feedback for correctness. Vet all peer suggestions against existing codebase constraints and project requirements before making any refactoring changes.

Does this code review response approach work for YAGNI principle violations in refactoring?▼

Yes, this code review response approach works for YAGNI principle violations by guiding you to verify the codebase and push back with technical evidence. It ensures feedback is technically verified against project requirements before any refactoring occurs.

When should I use a structured evaluation process for incoming code review feedback?▼

Use a structured evaluation process for incoming code review feedback whenever external or peer suggestions require vetting against existing codebase constraints. It is essential when feedback demands architectural alignment and strict technical accuracy before implementation.