receiving-code-review

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Respond to code review feedback with technical rigor, ensuring verification before implementing suggestions rather than blind agreement.

Core Features & Use Cases

  • Structured feedback parsing and requirement verification against codebase reality.
  • Stepwise pushback and technical justification for contentious changes.
  • Guided workflow that coordinates detection context, preamble outputs, and safe execution.

Quick Start

Review feedback using the defined workflow: read, understand, verify, evaluate, respond, and implement changes one 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 process code review feedback without blindly implementing suggestions?

Process code review feedback by applying a structured workflow: read, understand, verify, evaluate, and respond. This ensures feedback is truth-checked against the codebase before implementing changes, providing clear, testable justification for each modification.

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

The best way to push back on code review comments is through stepwise technical justification. Provide clear, testable justifications for your stance and ensure feedback is verified against codebase reality before agreeing to contentious changes.

How do I verify code review suggestions against my codebase?

Verify code review suggestions by parsing the feedback and checking the requirements against your codebase reality. Structured feedback parsing ensures modifications are truth-checked and validated before implementation.

When should I push back during a code review?

You should push back during a code review when feedback lacks technical rigor or does not align with codebase reality. The workflow ensures you evaluate feedback truth-checked against the codebase, providing clear justification for pushback when necessary.

What workflow should I follow to implement code review changes safely?

Follow a guided workflow to implement code review changes safely: read, understand, verify, evaluate, respond, and implement changes one at a time. This coordinates detection context and preamble outputs for safe execution.

Does receiving-code-review work for complex software projects?

Yes, receiving-code-review applies technical rigor to complex software projects by ensuring feedback is truth-checked against the codebase before implementing changes, providing clear, testable justification for each modification.