receiving-code-review

Verifies code review feedback against the codebase before implementing changes.

Updated Nov 4, 2022
One-click install
npx skills add https://github.com/CityBear3/dotfiles --skill receiving-code-review-citybear3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/CityBear3/dotfiles/tree/main/claude/skills/receiving-code-review
Command: npx skills add https://github.com/CityBear3/dotfiles --skill receiving-code-review-citybear3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you respond to code review feedback with technical rigor, ensuring you validate claims against the actual codebase instead of performing agreement or applying suggestions blindly.

Core Features & Use Cases

  • Structured evaluation loop: Read feedback fully, restate requirements, verify against the repository, and evaluate for correctness in context.
  • Clear response policy: Use technical acknowledgment or reasoned pushback, and avoid performative language or unverified implementation.
  • Triage decision guidance: Decide when to push back, create a fix task, or escalate based on whether the issue is minor, design- or architecture-altering, or out of plan scope.

Use it when an engineer, PR reviewer, or external reviewer delivers ambiguous or technically questionable review comments—especially when you need to confirm scope, rationale, and compatibility with existing decisions.

Quick Start

Use the receiving-code-review skill when you receive code review feedback to verify each suggestion against the codebase and implement only after clarification and validation.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I evaluate code review feedback before making changes?

Evaluating code review feedback requires verifying technical correctness against the codebase first. You must read feedback fully, restate requirements, verify claims against the repository, and evaluate correctness in context before implementing any suggested changes.

What's the best way to respond to PR feedback that conflicts with prior decisions?

Respond to conflicting PR feedback with reasoned pushback based on technical verification against the codebase. Avoid performative agreement or gratitude-only responses, and use explicit triage rules to decide whether to push back, fix, or escalate the issue.

How do I triage code review comments when scope is unclear?

Triage unclear code review comments by checking whether the issue is minor, design-altering, or out of plan scope. This determines whether you create a fix task, provide reasoned pushback, or escalate the feedback for further clarification.

When should I push back on reviewer suggestions instead of implementing them?

Push back on reviewer suggestions when technical verification against the codebase shows the feedback is incorrect or conflicts with prior architectural decisions. Use technical acknowledgment with explicit reasoning rather than performative agreement or blind implementation.

Can I use this structured review workflow for external reviewer reports?

Yes, the structured review workflow applies to both internal PR comments and external reviewer reports. It enforces a read-understand-verify-evaluate-respond-implement loop regardless of whether the feedback source is internal or external to your team.

Why do I need to verify code review suggestions against the actual codebase?

Verifying code review suggestions against the actual codebase prevents applying technically incorrect changes blindly. It ensures you validate claims, confirm scope and rationale, and check compatibility with existing decisions before writing any code.