receiving-code-review

Process code-review feedback through a six-step READ-UNDERSTAND-VERIFY-EVALUATE-RESPOND-IMPLEMENT workflow before modifying code.

4|Updated Oct 3, 2025
One-click install
npx skills add https://github.com/apexbusiness-systems/APEX-OmniHub --skill receiving-code-review-apexbusiness-systems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/apexbusiness-systems/APEX-OmniHub/tree/main/.cursor/superpowers/skills/receiving-code-review
Command: npx skills add https://github.com/apexbusiness-systems/APEX-OmniHub --skill receiving-code-review-apexbusiness-systems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews often yield vague or technically questionable feedback. This Skill provides a disciplined approach to interpret, verify, and act on feedback before modifying the code, reducing rework and risk.

Core Features & Use Cases

  • Structured feedback interpretation: Restate requirements in your own words to avoid misinterpretation.
  • Technical verification: Validate feedback against the actual codebase, tests, and dependencies.
  • Incremental implementation: Tackle items one at a time and verify each change.
  • Clear communication: Provide reasoned responses or pushback with technical justification.
  • Use case: When feedback says "optimize this" without specifics, restate the goal, measure impact, and propose concrete changes.

Quick Start

Read the feedback in full, restate the requirement, verify against the codebase, evaluate technical viability, respond with justification, and implement changes 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 vague code review feedback before changing my code?

Handle vague code review feedback by restating the requirement in your own words, verifying it against the codebase, evaluating technical viability, and then implementing changes one item at a time to reduce rework.

What is the best way to push back on technically questionable pull request comments?

Push back on questionable pull request comments by evaluating technical viability and providing reasoned responses with technical justification, ensuring you verify the feedback against actual tests and dependencies first.

Can I use a structured process to verify code review feedback across any codebase?

Yes, you can apply a structured six-step pattern—read, understand, verify, evaluate, respond, and implement—to process code review feedback with technical rigor across any codebase workflow.

How do I implement code review changes incrementally without introducing risk?

Implement code review changes incrementally by tackling feedback items one at a time and verifying each change against the codebase, ensuring per-item execution and technical verification before moving forward.

What should I do when a reviewer says optimize this without specific requirements?

When a reviewer says optimize this, restate the goal, measure the impact against the actual codebase, and propose concrete changes only after technical verification and evaluation of the feedback.