skills.rest
kxnzee
kxnzeeCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

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

Updated Aug 2, 2026
Search Tags:#code review#feedback#pull request#github#verification#yagni#pushback
One-click install
npx skills add https://github.com/kxnzee/multi-repo-specs --skill receiving-code-review-kxnzee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/kxnzee/multi-repo-specs/tree/main/extensions/superpowers/skills/receiving-code-review
Command: npx skills add https://github.com/kxnzee/multi-repo-specs --skill receiving-code-review-kxnzee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When receiving code review feedback, AI agents 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. - Pushback Guidance: Provides criteria for when and how to challenge incorrect suggestions using technical reasoning instead of blind compliance. - YAGNI Checks: Instructs verification of actual code usage before implementing "proper" features that nothing calls. - Use Case: A reviewer suggests removing legacy compatibility code. Instead of agreeing, the agent checks build targets, discovers the code is still required, and responds with the technical reason plus a targeted fix proposal. ## Quick Start Apply the receiving-code-review skill to evaluate the reviewer comments on my pull request before implementing any 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 agent?▼

Read the complete feedback, restate the requirement in your own words, verify it against the codebase, then implement one item at a time with testing. Avoid performative phrases like "great point" and let the code changes demonstrate understanding.

When should I push back on a code review 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 rather than being defensive.

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

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

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 confirm the reviewer understands the full context before implementing.

How do I reply to inline GitHub review comments?▼

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

Related Skills

Explore More Software Engineering Skills→
maxjuniorbrmaxjuniorbr
2

code-review-excellence

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

Community
Advanced
oncokboncokb

oncokb-verify-comments-are-addressed

Verifies whether GitHub pull request review comments are addressed and drafts prefixed replies.

Official
Intermediate
Open-PawsOpen-Paws
3

code-review

Automate layered code review for pull requests in CI pipelines.

Official
Advanced
carlos-algmscarlos-algms
2

replying-to-pr-review-threads

Reply to and resolve GitHub pull request review threads via GraphQL.

Community
Intermediate