receiving-code-review

Verify code review feedback against the codebase before implementing changes.

3|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/martin-janci/claude-marketplace --skill receiving-code-review-martin-janci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/martin-janci/claude-marketplace/tree/main/plugins/pr-toolkit/skills/receiving-code-review
Command: npx skills add https://github.com/martin-janci/claude-marketplace --skill receiving-code-review-martin-janci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Complete guidance for handling code review feedback, ensuring technical accuracy and avoiding performative agreement.

Core Features & Use Cases

  • Structured response pattern: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT steps for feedback.
  • Clarification-first workflow: prompts to ask questions when requirements are unclear before acting.
  • Guardrails for reviewers and developers: enforce technical reasoning, YAGNI, and context-aware pushback.

Quick Start

Restate the requirement, verify against the codebase, ask clarifying questions as needed, and implement one item 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 handle code review feedback without introducing new bugs?

Handle code review feedback by enforcing a verification step before implementation, ensuring technical correctness and minimal risk against the codebase. Apply a clarifying workflow to evaluate requirements before executing changes.

What is the best workflow for responding to unclear code review comments?

The best workflow for responding to unclear code review comments is clarification-first: restate the requirement, ask clarifying questions, verify against source code, and implement changes one item at a time.

How do I avoid performative agreement when addressing code review feedback?

Avoid performative agreement during code review by applying technical guardrails that enforce reasoning, YAGNI principles, and context-aware pushback before implementing requested changes.

What steps should I follow to implement code review changes safely?

To implement code review changes safely, follow a structured sequence: read, understand, verify, evaluate, respond, and implement, processing each modification individually to maintain technical accuracy.

When should I ask clarifying questions during a code review?

Ask clarifying questions during a code review whenever requirements are unclear or cannot be verified against the codebase, ensuring you understand the context before acting on any feedback.

Does this code review process support pushing back on reviewer requests?

Yes, this code review process supports pushing back on reviewer requests by evaluating feedback against source-driven guardrails and technical reasoning before agreeing to implement changes.