receiving-code-review

Verify code review feedback against the codebase and plan incremental changes.

9|2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/hongmaple0820/agent-academy --skill receiving-code-review-hongmaple0820
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/hongmaple0820/agent-academy/tree/main/skills/development/receiving-code-review
Command: npx skills add https://github.com/hongmaple0820/agent-academy --skill receiving-code-review-hongmaple0820

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When receiving code review feedback, teams often react emotionally or implement changes without verifying feasibility. This Skill enforces a disciplined, technically rigorous process to interpret feedback, verify against the codebase, and plan safe, incremental changes.

Core Features & Use Cases

  • Structured interpretation: Restate and verify every item from feedback before acting.
  • Technical pushback: Provide reasoned, codebase–specific rationale when feedback may be inappropriate or risky.
  • Incremental implementation: Break improvements into verifiable steps and test each item to prevent regressions.
  • Suitable for git PR reviews, pair programming debriefs, and code review acceptance criteria.

Quick Start

Restate each feedback item in your own words, verify it against the codebase, and plan one verifiable change at a time before implementation.

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 regressions?

Handle code review feedback by restating each item, verifying it against the current codebase, and planning incremental, verifiable changes to ensure safety and prevent regressions across different pull request contexts.

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

The best way to push back on pull request comments is to provide reasoned, codebase-specific technical rationale that verifies the feedback against current implementation constraints before refusing to implement the requested changes.

How do I verify if a code review suggestion is feasible for my codebase?

Verify a code review suggestion by interpreting the feedback, cross-referencing it against the existing codebase logic, and assessing potential risks to confirm feasibility before planning any incremental implementation steps.

Can I use a structured process to implement pull request changes step by step?

Yes, you can use a structured process to break pull request improvements into stepwise, verifiable actions, testing each item individually against the codebase to ensure safe and incremental implementation.

When should I not implement code review feedback directly?

You should not implement code review feedback directly when initial verification against the codebase reveals potential risks, inappropriate assumptions, or technical conflicts that require reasoned pushback before proceeding.

Does receiving-code-review work for pair programming debriefs and PR reviews?

Yes, receiving-code-review works for both pair programming debriefs and pull request reviews by enforcing a disciplined process to interpret feedback, verify technical constraints, and plan safe changes.