receiving-code-review

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

2|1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/passionseed/ps_app --skill receiving-code-review-passionseed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/passionseed/ps_app/tree/main/.agent/skills/receiving-code-review
Command: npx skills add https://github.com/passionseed/ps_app --skill receiving-code-review-passionseed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Process code review feedback in a disciplined, verifiable way to ensure understanding and validation before making changes.

Core Features & Use Cases

  • Restate and confirm requirements from feedback to ensure accurate understanding.
  • Verify each requested change against the current codebase and tests before implementation.
  • Push back with technical reasoning when feedback is unclear, incorrect, or risky.
  • Implement items one at a time, validating each change and avoiding blind agreement.
  • Facilitate clear, objective communication with human partners and external reviewers.

Quick Start

Read feedback items, restate requirements, verify against the codebase, and push back with technical reasoning before implementing 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 handle code review feedback that seems technically incorrect or unclear?

Handle code review feedback by restating requirements to confirm understanding, verifying requested changes against the codebase, and pushing back with technical reasoning when feedback is unclear or risky.

What is the best way to verify code review comments before implementing changes?

The best way to verify code review comments is to restate the feedback, check each requested change against the current codebase and tests, and implement items one at a time while validating each change incrementally.

Can I process code review feedback incrementally to avoid blind agreement?

Yes, process code review feedback incrementally by implementing items one at a time, validating each change against the codebase and tests, and avoiding blind agreement to ensure actions align with the codebase.

When should I restate requirements from code review feedback?

Restate requirements from code review feedback whenever comments are unclear, ambiguous, or technically questionable, ensuring accurate understanding and facilitating objective communication with reviewers before implementation.

What are the limitations of processing code review feedback automatically?

Processing code review feedback requires rigorous verification against the codebase before implementation; limitations arise when feedback lacks clarity or technical rigor, necessitating pushback with reasoning rather than blind agreement.