receiving-code-review

Verify code-review feedback against project requirements before implementing changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verification-first approach to code review feedback. Use when receiving review comments during the implement phase. Evaluate suggestions rigorously before implementing - no performative agreement.

Core Features & Use Cases

  • Restate requirements for clarity before acting.
  • Verify feedback against the codebase and assess technical soundness.
  • Push back with justification when suggestions conflict with project constraints.
  • Provide traceable, incremental changes and documentation.

Quick Start

Read each review in full, restate the request, verify it against the codebase, assess the technical implications, and respond with a factual, non-praise-based implementation plan.

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?

Verifying code-review feedback requires restating the requirements, checking suggestions against the codebase, and assessing technical soundness before applying incremental changes. This ensures modifications align with project constraints and maintain quality.

What is a verification-first approach to pull-request code reviews?

A verification-first approach evaluates review comments rigorously before implementation, avoiding performative agreement. It enforces precise restatement of requirements and an auditable, incremental implementation plan for every suggestion.

How do I push back on code-review suggestions that conflict with project constraints?

Pushing back on code-review suggestions requires factual justification based on codebase verification and technical implications. You provide traceable documentation explaining why the feedback conflicts with project requirements rather than blindly implementing changes.

What's the best way to document incremental implementation plans for code-review feedback?

Documenting incremental implementation plans involves restating each request, verifying it against the codebase, and providing traceable, justified changes across touched files. This creates an auditable record of how feedback was applied.

When should I not implement code-review feedback directly?

You should not implement code-review feedback when suggestions lack technical soundness or conflict with project constraints. The verification process identifies these cases, requiring you to push back with factual justification instead of performative agreement.

Can I apply code-review changes only within the implement phase?

Yes, applying code-review feedback occurs only within the implement phase across touched files. The process enforces rigorous evaluation, precise requirement restatement, and an auditable, incremental plan before any changes are made.