receiving-code-review

Guide engineers through code-review feedback using a six-step response pattern.

28.1k|5.0k|Updated Apr 8, 2020
One-click install
npx skills add https://github.com/srbhr/Resume-Matcher --skill receiving-code-review-srbhr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/srbhr/Resume-Matcher/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/srbhr/Resume-Matcher --skill receiving-code-review-srbhr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers navigate code-review feedback by prioritizing technical accuracy over courtesy or expediency, reducing misinterpretations and rework.

Core Features & Use Cases

  • Structured response pattern: Follow READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT to address each feedback item.
  • Clarification when unclear: ASK questions when feedback is ambiguous to avoid wrong implementations.
  • Reasoned pushback: Provide technical rationale when a suggested change is inappropriate for this codebase.
  • Incremental changes: Implement feedback one item at a time and test each change.

Quick Start

READ feedback fully before replying. UNDERSTAND: restate the requirement or request clarification if needed. VERIFY: check alignment with the codebase reality. EVALUATE: assess technical correctness for THIS codebase. RESPOND: provide technical acknowledgment or reasoned pushback. IMPLEMENT: apply one item at a time 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 to avoid implementing the wrong changes?

Handle code review feedback using a six-step pattern: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT. This ensures you assess technical correctness for your codebase before writing any code.

How do I process code review feedback before making changes?

Process code review feedback by first reading it fully, verifying alignment with codebase reality, evaluating technical correctness, and then implementing changes one item at a time with testing after each modification.

When should I push back on code review suggestions?

Push back on code review suggestions when a suggested change is inappropriate for your specific codebase. Provide a technical rationale and reasoned response instead of accepting feedback out of courtesy or expediency.

Does this code review process work for asynchronous reviews and pair programming?

Yes, this code review process works for asynchronous reviews and pair programming. It helps engineers prioritize technical accuracy across software projects to reduce misinterpretations and rework.

Why implement pull request feedback one item at a time?

Implement pull request feedback one item at a time to validate outcomes incrementally. Testing each change individually ensures modifications are correct and justified before moving to the next review item.

What is the receiving-code-review skill?

The receiving-code-review skill guides engineers to handle code-review feedback with technical rigor. It enforces a structured pattern to review feedback, reason about changes, and validate outcomes.