skills.rest
maopujie10-sys
maopujie10-sysCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Guides verification and reasoned responses when receiving code review feedback.

1|Updated Jun 24, 2026
Search Tags:#code review#feedback#pull request#github#verification#yagni#pushback
One-click install
npx skills add https://github.com/maopujie10-sys/Bailongma --skill receiving-code-review-maopujie10-sys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/maopujie10-sys/Bailongma/tree/main/src/skills/superpowers/receiving-code-review
Command: npx skills add https://github.com/maopujie10-sys/Bailongma --skill receiving-code-review-maopujie10-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents blind implementation and performative agreement when responding to code review feedback, ensuring every suggestion is technically verified against the actual codebase before changes are made. ## Core Features & Use Cases - Structured Response Pattern: Enforces a read-understand-verify-evaluate-respond-implement sequence for every piece of review feedback. - Pushback Guidance: Provides criteria for when and how to challenge incorrect suggestions with technical reasoning, including YAGNI checks for unused features. - Source-Specific Handling: Distinguishes between trusted feedback from your human partner and external reviewer suggestions that require extra skepticism. - Use Case: A reviewer asks you to remove legacy code. Instead of agreeing immediately, you check build targets, discover backward-compatibility constraints, and respond with a technically grounded question before changing anything. ## Quick Start Apply this skill whenever you receive code review comments so each suggestion is verified against the codebase before implementation.

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?▼

Read the full feedback, restate the requirement, verify it against the codebase, then respond with technical acknowledgment or reasoned pushback. Implement one item at a time and test each fix individually.

How do I handle unclear code review comments?▼

Stop and ask for clarification before implementing anything. Partial understanding leads to wrong implementations, so confirm every unclear item first, even if other items are clear.

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 your stack, or conflicts with prior architectural decisions. Use technical reasoning and reference working code or tests.

Should I implement external reviewer feedback immediately?▼

No. External feedback should be treated as suggestions to evaluate, not orders. Check technical correctness for your codebase, platform compatibility, and whether the reviewer understands the full context before implementing.

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

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.

Related Skills

Explore More Software Engineering Skills→
Archive228Archive228
746

pr-from-diff

Generate structured pull request descriptions from commit messages and changes.

Community
Basic
beekeeper-labbeekeeper-lab
1

Deploy

Promote a test branch to main via pull request after tests and lint pass.

Community
Advanced
Open-PawsOpen-Paws
3

code-review

Automate layered code review for pull requests in CI pipelines.

Official
Advanced
sizukutamagosizukutamago

codex-collab

Coordinate Claude Code and Codex in tmux panes for design reviews.

Community
Advanced