receiving-code-review

Verify code review feedback against the codebase before implementing changes.

1|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/mealpac/manus --skill receiving-code-review-mealpac
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/mealpac/manus/tree/main/skills/workflow-skills/receiving-code-review
Command: npx skills add https://github.com/mealpac/manus --skill receiving-code-review-mealpac

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews often mix social signals with technical guidance, which can lead to misinterpretation and sloppy changes. This Skill provides a structured, repeatable process to verify feedback before implementing it.

Core Features & Use Cases

  • Enforces a six-step response pattern: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT to maintain technical rigor.
  • Guides handling unclear feedback with a formal escalation and clarification process.
  • Includes source-specific handling rules and pushback guidelines to preserve code integrity.

Quick Start

Read the feedback, restate the requirement in your own words, verify it against the codebase, evaluate its technical validity, respond with reasoning, 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 code-review feedback without introducing sloppy changes?

Handle code-review feedback by enforcing a six-step technical validation pattern before implementation. This process separates social signals from technical guidance, ensuring review feedback leads to technically sound implementations and preserves code integrity.

What is the best way to respond to pull request comments technically?

The best way to respond to pull request comments is using a structured pattern: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT. This maintains technical rigor by verifying feedback against the codebase before writing any code.

How do I verify unclear code review feedback before implementing changes?

Verify unclear code review feedback through a formal escalation and clarification process. Restate the requirement in your own words, evaluate its technical validity against the codebase, and request clarification before proceeding with implementation.

When should I push back on code review suggestions?

Push back on code review suggestions when technical evaluation reveals validity issues. Apply strict pushback guidelines and source-specific handling rules during the verification phase to ensure requested changes do not compromise code quality.

Can I use a structured process to manage pull request reviews for software engineering?

Yes, you can use a structured six-step verification process to manage pull request reviews. This software engineering workflow enforces technical rigor and source-aware handling, ensuring every piece of feedback is validated before changes are implemented.