skills.rest
jmmL
jmmLCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Process code-review feedback through a six-step READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT pattern.

Updated Jan 8, 2026
Search Tags:#testing#communication#verification#code-review#pull-request#technical-rigor#incremental-implementation
One-click install
npx skills add https://github.com/jmmL/dr3-old --skill receiving-code-review-jmml
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/jmmL/dr3-old/tree/main/.claude/skills/receiving-code-review
Command: npx skills add https://github.com/jmmL/dr3-old --skill receiving-code-review-jmml

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you handle code-review feedback with technical rigor before implementing changes.

Core Features & Use Cases

  • Read and understand feedback without reacting emotionally.
  • VERIFY against the codebase reality to confirm what is needed.
  • Provide reasoned pushback when suggestions are technically questionable.
  • Implement items one at a time, with focused tests to avoid regressions.
  • Ask clarifying questions when requirements are unclear to avoid misinterpretation.

Quick Start

  • When feedback arrives, follow the six-step pattern: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT.
  • Always restate the requirement or ask for clarification if anything is unclear before acting.
  • Verify each suggested change against the project codebase and tests, then implement it incrementally and test each change.

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 reacting emotionally?▼

Handle code-review feedback by first reading and understanding the input objectively. You process suggestions through a structured six-step pattern, ensuring technical rigor before implementing any changes to your pull request.

What is the best way to verify code-review suggestions against my codebase?▼

Verify code-review suggestions by checking them against your codebase reality before acting. You confirm what is actually needed, evaluate the technical validity of the feedback, and provide reasoned pushback if suggestions are questionable.

How do I implement code-review changes incrementally to avoid regressions?▼

Implement code-review changes incrementally by processing one item at a time with focused tests. You respond to feedback individually, apply the changes step by step, and run tests for each modification to prevent regressions.

When should I ask clarifying questions during a code review?▼

Ask clarifying questions during a code review when requirements are unclear to avoid misinterpretation. You should restate the requirement or request clarification before acting on any feedback to ensure accurate implementation.

Does this code-review approach work for pull requests with multiple items?▼

Yes, this approach works for pull requests with multiple items by enforcing one-item-at-a-time changes. You read, understand, verify, evaluate, respond, and implement for each piece of feedback sequentially to maintain technical rigor.

Related Skills

Explore More Software Engineering Skills→
Shresth-shShresth-sh

receiving-code-review

Verify code-review feedback against the codebase before implementing changes.

Community
Intermediate
SkogAISkogAI
1

receiving-code-review

Evaluate code review feedback against the codebase before implementing changes.

Official
Intermediate
jagreehaljagreehal
3

code-review-reception

Validate code review feedback against the codebase before incremental implementation.

Community
Basic
bnadlerjrbnadlerjr
5

receiving-code-review

Evaluate code-review feedback for technical correctness before implementation.

Community
Intermediate