receiving-code-review

Evaluate and verify code review feedback before implementation.

134|12|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/6BNBN/FlowPilot --skill receiving-code-review-6bnbn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/6BNBN/FlowPilot/tree/main/%E5%85%BC%E5%AE%B9codex%40cursor%E4%B8%80%E9%94%AE%E5%AE%89%E8%A3%85%E6%8A%80%E8%83%BD/codex%E4%B8%80%E9%94%AE%E5%AE%89%E8%A3%85%E6%8A%80%E8%83%BD/.codex-home-claude-parity/skills/receiving-code-review
Command: npx skills add https://github.com/6BNBN/FlowPilot --skill receiving-code-review-6bnbn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that code review feedback is technically evaluated and verified before implementation, preventing blind acceptance of potentially incorrect or contextually inappropriate suggestions.

Core Features & Use Cases

  • Technical Verification: Empowers users to rigorously check feedback against codebase realities and project requirements.
  • Reasoned Pushback: Facilitates constructive technical disagreement when feedback is flawed or lacks context.
  • Use Case: When a reviewer suggests a change, this Skill guides you to first verify its technical soundness, check for regressions, and understand its necessity within the project's scope before making any modifications.

Quick Start

When receiving code review feedback, verify each item technically before implementing any suggestions.

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 technical feedback before implementing code review changes?

Verify code review feedback by rigorously checking each suggestion against codebase realities and project requirements. This process ensures technical soundness, identifies potential regressions, and validates contextual necessity before modifying any code.

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

Pushing back on code review feedback requires reasoned technical arguments grounded in codebase reality. Constructive disagreement involves questioning unclear suggestions, verifying correctness, and prioritizing project-specific context over performative agreement.

Why should I question code review feedback instead of implementing it directly?

Questioning code review feedback prevents blind acceptance of potentially incorrect or contextually inappropriate suggestions. Evaluating technical soundness ensures code quality, correctness, and prevents regressions that performative agreement might introduce.

How do I check if code review comments will cause regressions in my software development workflow?

Checking for regressions involves verifying code review feedback against codebase reality and project scope. Rigorous technical verification ensures suggested modifications maintain correctness and do not disrupt existing software development functionality.

When should I not apply code review feedback in software development?

You should not apply code review feedback when suggestions lack technical soundness, fail verification against codebase reality, or ignore project-specific context. Reasoned pushback is necessary when feedback introduces regressions or contextually inappropriate changes.