skills.rest
bearhedge
bearhedgeCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Manage code-review feedback with a six-step response pattern.

Updated Aug 23, 2026
Search Tags:#verification#quality-assurance#pushback#code-review#pull-request#technical-rigor
One-click install
npx skills add https://github.com/bearhedge/APE-YOLO --skill receiving-code-review-bearhedge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/bearhedge/APE-YOLO/tree/main/.claude/skills/receiving-code-review
Command: npx skills add https://github.com/bearhedge/APE-YOLO --skill receiving-code-review-bearhedge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams manage code-review feedback with technical rigor before implementing changes.

Core Features & Use Cases

  • Structured response pattern: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT.
  • Clarify and push back: Demand clarification or provide technical reasoning when feedback is unclear or risky.
  • Incremental changes: Implement items one at a time, with verification and testing to prevent regressions.
  • Use Case: When a reviewer asks for changes, this Skill guides you to restate requirements, check against the codebase, and respond with justification.

Quick Start

  • Read the feedback in detail.
  • Restate the requirement in your own words or ask for clarification.
  • Verify against the codebase and propose a concrete implementation plan.

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 unclear code review feedback on a pull request?▼

Handle unclear code review feedback by restating the requirement in your own words and demanding clarification. You must verify the suggestion against the codebase and evaluate its risk before responding with technical reasoning.

What is the structured process for responding to code review comments?▼

The structured process for responding to code review comments follows a six-step pattern: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT. This enforces technical rigor and prevents regressions during iterative development.

How do I push back on risky pull request changes without causing conflict?▼

Push back on risky pull request changes by providing concrete technical reasoning after verifying the feedback against your codebase. Evaluate the risk, justify your position, and propose a safe, incremental implementation plan.

Should I implement all code review changes at once or one at a time?▼

You should implement code review changes one item at a time. Incremental changes with continuous verification and testing prevent regressions and ensure technical rigor throughout the pull request process.

What should I do when code review feedback conflicts with the existing codebase?▼

When code review feedback conflicts with the existing codebase, verify the proposed change against the actual code, evaluate the technical risk, and respond with justification or push back with a concrete alternative implementation plan.

Does the receiving-code-review Skill support iterative development workflows?▼

Yes, the receiving-code-review Skill supports iterative development workflows. It manages pull request feedback by enforcing verification and one-item-at-a-time implementation to handle unclear or conflicting review comments safely.

Related Skills

Explore More Software Engineering Skills→
ZESCODEZESCODE

ZES-receiving-code-review

Verifies incoming pull request feedback before implementing any code changes.

Community
Advanced
diarworlddiarworld
6

ai-factory.fix

Investigate error messages and implement code fixes with logging and test suggestions.

Community
Advanced
vanhoangkhavanhoangkha

prowler-compliance-review

Validate compliance framework JSON syntax, check existence, and verify requirement ID uniqueness in pull requests.

Community
Intermediate
srnnklssrnnkls

code-review-receive

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

Community
Advanced