skills.rest
mpmf
mpmfCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

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

Updated May 28, 2026
Search Tags:#code review#feedback#pull request#github#verification#yagni#pushback
One-click install
npx skills add https://github.com/mpmf/SDD_Base --skill receiving-code-review-mpmf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/mpmf/SDD_Base/tree/main/.opencode/skills/superpowers/receiving-code-review
Command: npx skills add https://github.com/mpmf/SDD_Base --skill receiving-code-review-mpmf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When receiving code review feedback, AI assistants often respond with performative agreement or blindly implement suggestions without verifying them against the actual codebase, leading to broken functionality, unnecessary features, and wasted effort. ## Core Features & Use Cases - Structured Response Pattern: Enforces a read-understand-verify-evaluate-respond-implement workflow for every piece of review feedback. - Source-Specific Handling: Applies different trust levels for feedback from your human partner versus external reviewers, with explicit verification checklists. - Pushback and YAGNI Guidance: Provides concrete rules for pushing back on technically incorrect suggestions and rejecting unused features. - Use Case: A reviewer suggests removing legacy code. Instead of agreeing, you check the build target, discover backward compatibility requirements, and respond with technical reasoning before acting. ## Quick Start Use the receiving-code-review skill to evaluate this pull request feedback before implementing any of the suggested changes.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How should I respond to code review feedback as an AI assistant?▼

Read the complete feedback, restate the requirement, verify it against the codebase, then respond with technical acknowledgment or reasoned pushback. Avoid performative phrases like "You're absolutely right" and implement one item at a time with testing.

What should I do when code review feedback is unclear?▼

Stop and ask for clarification before implementing anything. Partial understanding leads to wrong implementations, so state which items you understand and request clarification on the rest before proceeding.

When should I push back on a reviewer's suggestion?▼

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

How do I handle external reviewer feedback differently from my team lead?▼

Treat external feedback as suggestions to evaluate, not orders. Verify technical correctness for your codebase, check for regressions and platform compatibility, and consult your human partner if feedback conflicts with their prior decisions.

How do I reply to inline review comments on GitHub pull requests?▼

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 code line being reviewed.

Related Skills

Explore More Software Engineering Skills→
maxjuniorbrmaxjuniorbr
2

code-review-excellence

Provide structured, actionable feedback for code reviews and mentoring sessions.

Community
Advanced
JYeswakJYeswak

pr-verify

Verifies patches by running the reproduction before and after the change.

Community
Intermediate
Open-PawsOpen-Paws
3

code-review

Automate layered code review for pull requests in CI pipelines.

Official
Advanced
edpagetedpaget

review

Review code changes against architectural principles and detect semantic violations.

Community
Advanced