skills.rest
woodrowpearson
woodrowpearsonCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

receiving-code-review

Respond to code review feedback using a six-step verification process.

Updated Jul 14, 2025
Search Tags:#verification#clarification#quality-assurance#code-review#pull-request#change-management#technical-rigor
One-click install
npx skills add https://github.com/woodrowpearson/mids-hero-web --skill receiving-code-review-woodrowpearson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/woodrowpearson/mids-hero-web/tree/main/.claude/skills/receiving-code-review
Command: npx skills add https://github.com/woodrowpearson/mids-hero-web --skill receiving-code-review-woodrowpearson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides how to respond to code review feedback with technical rigor before implementing changes.

Core Features & Use Cases

  • Clear response pattern: FOLLOW six-step process (READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT) to avoid blind agreement.
  • Clarification-first approach: STOP and ask for clarification when feedback is unclear or ambiguous.
  • Codebase verification: Verify requirements against the actual codebase before making changes to ensure correctness.

Quick Start

WHEN you receive code review feedback, apply the six-step pattern to determine the exact changes to implement and verify against the repository before applying them.

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 blindly accepting every change request?▼

To handle code review feedback effectively, follow a six-step pattern: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT. This enforces technical rigor by requiring codebase verification before making changes.

What is the best way to respond to ambiguous or unclear code review comments?▼

The best way to respond to unclear code review comments is to stop and ask for clarification immediately. You must ensure technical rigor by fully understanding the feedback before evaluating or implementing any changes.

How do I verify pull request feedback against the actual repository before implementing changes?▼

To verify pull request feedback against the repository, evaluate the requested changes within the codebase context. This change-management step ensures requirements are technically sound and verifiable before you apply modifications.

When should I ask for clarification during a multi-item code review?▼

You should ask for clarification during a multi-item code review whenever feedback is ambiguous. Pausing to clarify requirements prevents incorrect implementations and enforces technical rigor before you proceed with code changes.

Does this code review response process work for multi-item pull request feedback across software projects?▼

Yes, this code review response process handles multi-item requests across software projects. It applies a structured six-step pattern to evaluate each item, ensuring correct and verifiable results before implementation.

Why verify codebase requirements before implementing code review changes?▼

Verifying codebase requirements before implementing code review changes ensures correctness and prevents blind agreement. Evaluating feedback against actual code maintains technical rigor and yields verifiable, accurate results.

Related Skills

Explore More Software Engineering Skills→
awinogradovawinogradov
5

pr:resolve

Analyze pull request comments, apply code fixes, and reply to reviewers via GitHub API.

Community
Advanced
mcampbellrmcampbellr

gsd-pr-branch

Remove .planning/ commits from a branch to create a clean pull request branch.

Community
Basic
the-inconvenience-storethe-inconvenience-store
1

receiving-code-review

Evaluate and implement code review feedback with technical rigor.

Community
Intermediate
voidrotvoidrot

python-code-style

Format and lint Python source code with Black, Ruff, isort, and mypy.

Community
Advanced