skills.rest
macintorsten
macintorstenCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

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

Updated Dec 23, 2025
Search Tags:#code review#feedback#pull request#YAGNI#github#verification#pushback
One-click install
npx skills add https://github.com/macintorsten/aurapod --skill receiving-code-review-macintorsten
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/macintorsten/aurapod/tree/main/.github/skills/receiving-code-review
Command: npx skills add https://github.com/macintorsten/aurapod --skill receiving-code-review-macintorsten

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents blind implementation of code review feedback by enforcing a verify-first workflow, eliminating performative agreement and technically unsound changes. ## Core Features & Use Cases - Structured Response Pattern: Read, understand, verify, evaluate, respond, and implement feedback one item at a time with individual testing. - Source-Specific Handling: Applies different trust levels for feedback from your human partner versus external reviewers, with pushback guidance. - YAGNI and Unclear Feedback Checks: Greps the codebase for actual usage before adding features and stops to clarify ambiguous items before implementing. - Use Case: When a reviewer suggests removing legacy code or adding a metrics endpoint, verify against the codebase reality first, then implement or push back with technical reasoning. ## Quick Start Use the receiving-code-review skill to evaluate and respond to the review comments on my pull request.

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 implement or push back with reasoning. Avoid performative phrases like "You're absolutely right" and let the code changes demonstrate you heard the feedback.

How to handle unclear code review comments before implementing?▼

Stop and ask for clarification on all unclear items before implementing anything. Partial understanding leads to wrong implementations because feedback items are often related.

Should I implement every suggestion from external reviewers?▼

No. External feedback is a suggestion to evaluate, not an order. Check whether it is technically correct for your codebase, breaks existing functionality, or conflicts with prior architectural decisions before implementing.

When should I push back on code review feedback?▼

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

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→
maxjuniorbrmaxjuniorbr
2

code-review-excellence

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

Community
Advanced
racecraft-labracecraft-lab
3

speckit-resolve-pr

Resolve unresolved pull request review threads with minimal code changes.

Official
Advanced
erfanzarerfanzar
27

requesting-code-review

Automate pre-commit code review with static checks, linting, and auto-fixes.

Community
Advanced
acmelemeacmeleme

pr-review-response

Post replies to PR review threads referencing fixes and optionally resolve them.

Official
Intermediate