receiving-code-review

Process code review feedback through read-verify-evaluate-respond-implement steps.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/koseki2580/skills --skill receiving-code-review-koseki2580
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/koseki2580/skills/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/koseki2580/skills --skill receiving-code-review-koseki2580

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents incorrect, premature, or performative changes by ensuring you process code review feedback as a technical evaluation workflow before implementing anything.

Core Features & Use Cases

  • Structured reception workflow: Read feedback fully, restate requirements, verify against the codebase, then evaluate and respond technically.
  • Clarification-first safety: Stops implementation when any item is unclear and asks for clarification to avoid partial misunderstanding.
  • Phrasing discipline for GitHub/threads: Uses specific non-performative language rules and avoids gratitude/apologies in favor of concrete, verifiable actions.
  • Implementation sequencing & testing: Implements multi-item feedback one item at a time with tests and regression checks, prioritizing blocking issues first.
  • YAGNI and pushback handling: Checks actual code usage, avoids adding unused “proper” features, and pushes back with technical reasoning when suggestions conflict with reality or prior decisions.

Quick Start

Ask your AI to process incoming code review comments using the skill’s verify-first pattern, requesting clarification for any unclear items before making 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 process code review feedback without making premature changes?

Process code review feedback by following a read-understand-verify-evaluate-respond-implement workflow. This ensures you restate requirements, verify against the codebase, and evaluate technically before writing any code, preventing incorrect or performative modifications.

How do I handle multi-item PR feedback on GitHub systematically?

Handle multi-item PR feedback by sequencing implementation one item at a time. Prioritize blocking issues first, apply per-fix testing and regression checks, and use clarification-first safety to stop implementation if any inline comment or thread item is unclear.

When should I push back on a code review suggestion?

Push back on code review suggestions when they conflict with reality or prior technical decisions. Use technical reasoning to justify your response, apply YAGNI checks to avoid adding unused proper features, and verify actual code usage before agreeing to changes.

What is the best way to respond to GitHub inline comment replies professionally?

Respond to GitHub inline comments using non-performative phrasing discipline. Avoid gratitude and apologies, favoring concrete, verifiable actions that state exactly what fix or verification step will be implemented next.

Does implementing code review feedback require testing for each fix?

Yes, implementing code review feedback requires ordered implementation with per-fix testing. You must sequence multi-item feedback individually, applying tests and regression checks after each fix to ensure verified changes and prevent partial misunderstandings.