skills.rest
ibytechaos
ibytechaosCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

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

1|Updated Oct 11, 2025
Search Tags:#code review#feedback#pull request#github#verification#yagni#pushback
One-click install
npx skills add https://github.com/ibytechaos/claude --skill receiving-code-review-ibytechaos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/ibytechaos/claude/tree/main/plugins/superpowers/skills/receiving-code-review
Command: npx skills add https://github.com/ibytechaos/claude --skill receiving-code-review-ibytechaos

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. - Pushback Guidance: Provides concrete criteria for when and how to challenge incorrect or context-lacking reviewer suggestions with technical reasoning. - YAGNI Enforcement: Checks whether suggested features are actually used in the codebase before implementing them. - Use Case: A reviewer on your pull request suggests removing legacy compatibility code. Instead of agreeing immediately, you verify the build targets and discover the code is still required, then reply with the technical evidence. ## Quick Start Apply the receiving-code-review skill to evaluate the review comments on my current 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 assistant?▼

Read the complete feedback, restate the requirement, verify it against the codebase, then implement one item at a time with testing. Avoid performative phrases like "great point" and use technical acknowledgment or reasoned pushback instead.

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.

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 code review feedback from external reviewers?▼

Treat external feedback as suggestions to evaluate, not orders. Check whether it is technically correct for your codebase, breaks existing functionality, and whether the reviewer understands the full context before implementing.

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 rather than posting a top-level PR comment. This keeps the discussion attached to the specific code line.

Related Skills

Explore More Software Engineering Skills→
haojing8312haojing8312
154

receiving-code-review

Verify code review feedback before implementing changes in pull requests.

Community
Intermediate
SeanHoggSeanHogg
3

prepare-pr

Rebase a GitHub Pull Request onto main, fix review findings, run gates, and push.

Community
Advanced
Open-PawsOpen-Paws
3

code-review

Automate layered code review for pull requests in CI pipelines.

Official
Advanced
gvarelagvarela
1

review-prep

Orchestrate interactive code reviews with tmux and neovim.

Community
Intermediate