receiving-code-review

Guides verification and implementation of code review feedback with technical rigor.

Updated Jul 22, 2026
One-click install
npx skills add https://github.com/johnstegeman/pi-packages --skill receiving-code-review-johnstegeman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/johnstegeman/pi-packages/tree/main/packages/pi-superpowers-plus/skills/receiving-code-review
Command: npx skills add https://github.com/johnstegeman/pi-packages --skill receiving-code-review-johnstegeman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Receiving code review feedback often leads to performative agreement, blind implementation of questionable suggestions, or partial fixes when items are unclear. This Skill enforces a verify-before-implement workflow so review feedback is evaluated against the actual codebase before any changes are made. ## Core Features & Use Cases - Structured Response Pattern: Read, understand, verify, evaluate, respond, then implement feedback one item at a time with individual testing. - Source-Specific Handling: Different rules for trusted human partner feedback versus external reviewer suggestions, including pushback with technical reasoning when suggestions are wrong. - YAGNI and Clarification Checks: Grep the codebase for actual usage before implementing "proper" features, and stop to ask when any feedback item is unclear. - Use Case: A reviewer leaves six comments on your pull request, two of which are ambiguous and one of which suggests removing legacy code needed for backward compatibility. The Skill guides you to clarify the ambiguous items first, push back on the legacy removal with technical evidence, and implement the rest one at a time with tests. ## Quick Start Use the receiving-code-review skill to help me evaluate and respond to the review comments on my current pull request before implementing anything.

Frequently Asked Questions about receiving-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I respond to code review feedback professionally?

Respond with technical acknowledgment or silent fixes instead of performative agreement like "You're absolutely right!" Restate the requirement, verify it against the codebase, then either implement it or push back with technical reasoning.

How to handle unclear code review comments?

Stop and ask for clarification before implementing anything when any feedback item is unclear. Partial understanding leads to wrong implementations, especially when items are related, so clarify all ambiguous items first.

When should I push back on code review suggestions?

Push back when a suggestion breaks existing functionality, violates YAGNI for unused features, is technically incorrect for your stack, or conflicts with prior architectural decisions. Use technical reasoning and reference working tests or code, not defensiveness.

Should I implement all code review feedback at once?

No, implement one item at a time and test each fix individually. Order work by blocking issues first, then simple fixes, then complex refactoring, and verify no regressions after each change.

How do I reply to inline GitHub review comments?

Reply within the comment thread using the GitHub API endpoint for pull request comment replies, not as a top-level PR comment. This keeps the discussion attached to the specific line of code being reviewed.