skills.rest
NT-boop-star
NT-boop-starCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

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

Updated Apr 7, 2026
Search Tags:#code review#feedback#pull request#github#verification#yagni#pushback
One-click install
npx skills add https://github.com/NT-boop-star/BRMV-tract --skill receiving-code-review-nt-boop-star
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/NT-boop-star/BRMV-tract/tree/main/antigravity/skills/receiving-code-review
Command: npx skills add https://github.com/NT-boop-star/BRMV-tract --skill receiving-code-review-nt-boop-star

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Receiving code review feedback often triggers performative agreement or blind implementation, leading to broken code, wasted effort on unnecessary features, and missed clarification on unclear items. This Skill enforces a verify-before-implement discipline when handling review comments. ## Core Features & Use Cases - Structured Response Pattern: Read, understand, verify against the codebase, evaluate, respond, then implement one item at a time with individual testing. - Source-Specific Handling: Different rules for trusted human partner feedback versus external reviewer suggestions, including pushback criteria and YAGNI checks. - Use Case: A reviewer suggests removing legacy code or adding a metrics endpoint. Instead of agreeing immediately, you grep the codebase, discover backward-compatibility constraints or zero callers, and respond with technical reasoning or a YAGNI challenge. ## Quick Start Use the receiving-code-review skill to help me evaluate and respond to this pull request review feedback 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?▼

Restate the technical requirement, verify it against the codebase, then either implement with a brief factual acknowledgment or push back with technical reasoning. Avoid performative phrases like "Great point!" and let the code change demonstrate you heard the feedback.

How to handle unclear code review comments before implementing?▼

Stop and ask for clarification on every unclear item before implementing anything. Partial understanding leads to wrong implementations because feedback items are often related, so clarify all items first, then implement in order of blocking issues, simple fixes, and complex fixes.

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

Should I implement every external reviewer suggestion on a pull request?▼

No. External feedback is a suggestion to evaluate, not an order. 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, not as a top-level PR comment. This keeps the discussion attached to the specific line of code being reviewed.

Related Skills

Explore More Software Engineering Skills→
LAF-USLAF-US

gh-address-comments

Cluster GitHub PR feedback by file and apply traceable fixes.

Official
Intermediate
rizqinrrrizqinrr
665

code-review-and-quality

Reviews code changes across correctness, readability, architecture, security, and performance before merge.

Community
Advanced
Open-PawsOpen-Paws
3

code-review

Automate layered code review for pull requests in CI pipelines.

Official
Advanced
summarybotngsummarybotng
2

code-review-quality

Conduct context-driven code reviews focusing on quality, testability, and maintainability.

Official
Advanced