skills.rest
mortenbroesby
mortenbroesbyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

receiving-code-review

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

1|Updated Apr 5, 2026
Search Tags:#feedback#communication#verification#risk-assessment#code-review#pull-request#technical-judgment
One-click install
npx skills add https://github.com/mortenbroesby/playground --skill receiving-code-review-mortenbroesby
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/mortenbroesby/playground/tree/main/.skills/receiving-code-review
Command: npx skills add https://github.com/mortenbroesby/playground --skill receiving-code-review-mortenbroesby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review requires technical evaluation, not emotional performance. This guide helps ensure feedback is verified before implementing changes.

Core Features & Use Cases

  • Clarify requirements when feedback is unclear and restate the technical need.
  • Verify changes by checking the codebase, tests, and project constraints before acting.
  • Implement feedback incrementally, one item at a time, with justification and test validation.

Quick Start

Ask clarifying questions and verify feedback before starting any changes.

Frequently Asked Questions about receiving-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify code-review feedback before implementing changes?▼

Verify code-review feedback by clarifying unclear requirements, checking the codebase and tests against project constraints, and outlining a safe implementation plan before acting. Validate technical correctness to ensure changes are justified and testable.

What is the best way to handle unclear code review comments on a pull request?▼

Handle unclear code review comments by asking clarifying questions and restating the technical need. Verify the requested changes against the codebase and project constraints before starting any implementation to ensure technical correctness.

How do I implement code review feedback safely without breaking tests?▼

Implement code review feedback safely by applying changes one item at a time with justification and test validation. Outline a safe implementation plan and conform to safety checks to ensure testable outcomes for each incremental change.

When should I not implement pull request feedback directly?▼

Do not implement pull request feedback directly when requirements are unclear or unverified. Withhold implementation until you have clarified the technical need, verified the change against the codebase, and confirmed it passes project constraint checks.

What does a safe implementation plan for code review changes look like?▼

A safe implementation plan for code review changes involves clarifying requirements, verifying feedback against the codebase, and applying changes one item at a time with test validation. This ensures technical correctness and testable outcomes before finalizing.

Related Skills

Explore More Software Engineering Skills→
chokky-educationchokky-education

receiving-code-review

Standardizes incoming code review feedback verification and technical response preparation for pull requests and peer sessions.

Community
Intermediate
izyanrajwaniizyanrajwani
4

receiving-code-review

Restate code-review feedback and implement verified changes one at a time.

Community
Intermediate
EotelEotel

refactor-clean

Identify and remove dead code with test verification and rollback.

Community
Intermediate
fartmonarchfartmonarch
1

receiving-code-review

Validate code review feedback against the codebase before implementing changes.

Community
Intermediate