receiving-code-review

Verify unclear code-review feedback against the codebase before implementing changes.

3|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/mor-duongmh/morkit-plugin --skill receiving-code-review-mor-duongmh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/mor-duongmh/morkit-plugin/tree/main/plugins/morkit/skills/receiving-code-review
Command: npx skills add https://github.com/mor-duongmh/morkit-plugin --skill receiving-code-review-mor-duongmh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review feedback is often unclear or technically dubious; this Skill helps ensure you verify and validate before implementing, avoiding blind agreement.

Core Features & Use Cases

  • Read, understand, verify against the codebase, and evaluate technical correctness before acting.
  • Push back with technical reasoning when feedback is unclear or potentially incorrect.
  • Implement items one at a time, with targeted tests to prevent regressions.

Quick Start

Read the feedback in full, verify it against the codebase, and implement changes one at a time with tests.

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 reading it in full, verifying claims against the codebase, and evaluating technical correctness before implementing any changes. This prevents blind agreement and ensures ambiguous comments are resolved with technical rigor.

What is the best way to push back on technically dubious code review comments?

Push back on technically dubious code review comments by verifying the feedback against your codebase and formulating a structured response with technical reasoning. This ensures you address incorrect feedback with evidence rather than implementing unnecessary changes.

How do I implement code review changes without introducing regressions?

Implement code review changes without regressions by addressing items one at a time with targeted tests. This incremental approach validates each modification against the codebase before moving to the next feedback item.

When should I verify feedback against the codebase before making changes?

Verify feedback against the codebase whenever you receive code review comments on a pull request. This structured verification step identifies technically questionable feedback and confirms the necessity of changes before you start implementing.

Does resolving code review feedback require a structured response pattern?

Resolving code review feedback requires a structured response pattern of reading, understanding, verifying, evaluating, responding, and implementing. This ensures codebase verification and incremental changes are applied systematically.