skills.rest
shekohex
shekohexCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Process code review feedback by verifying, evaluating, and implementing suggestions.

9|Updated Aug 12, 2025
Search Tags:#code review#feedback#implementation#verification#technical rigor#pushback
One-click install
npx skills add https://github.com/shekohex/dotai --skill receiving-code-review-shekohex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/shekohex/dotai/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/shekohex/dotai --skill receiving-code-review-shekohex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you process code review feedback effectively, ensuring technical rigor and avoiding performative agreement or blind implementation. It guides you to verify suggestions before acting, especially when feedback is unclear or questionable.

Core Features & Use Cases

  • Structured Response Pattern: Follows a clear process: Read, Understand, Verify, Evaluate, Respond, Implement.
  • Handling Ambiguity: Provides clear steps for asking clarification when feedback is unclear.
  • External Reviewer Scrutiny: Outlines checks for external feedback, including technical correctness, impact on existing functionality, and reviewer context.
  • YAGNI Principle: Guides the evaluation of suggestions against actual codebase usage.
  • Graceful Pushback & Correction: Offers strategies for technical pushback and for correcting your own incorrect pushbacks.

Quick Start

When receiving code review feedback, verify technical soundness before implementing suggestions.

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 without just blindly implementing suggestions?▼

To respond to code review feedback effectively, follow a structured process: Read, Understand, Verify, Evaluate, Respond, and Implement. This ensures technical rigor by verifying technical soundness before acting on any suggestions.

What is the best way to ask for clarification when code review feedback is unclear?▼

When code review feedback is unclear, the best way to ask for clarification is to follow specific steps designed to handle ambiguity. This approach ensures you fully understand the reviewer's intent before attempting any implementation.

How do I evaluate external code review suggestions against my existing codebase?▼

To evaluate external code review suggestions, perform checks for technical correctness, impact on existing functionality, and reviewer context. This scrutiny ensures external feedback does not negatively disrupt your current system.

When should I push back on code review feedback?▼

You should push back on code review feedback using reasoned technical arguments after verifying the suggestion's soundness. This includes evaluating proposals against the YAGNI principle and actual codebase usage to avoid unnecessary additions.

How do I correct my pushback if I was wrong during a code review?▼

To correct your pushback during a code review, use graceful correction strategies. This involves acknowledging the reviewer's valid points and adjusting your implementation approach while maintaining technical rigor.

Related Skills

Explore More Software Engineering Skills→
hideki5123hideki5123
2

address-pr-comments

Fetch and apply AI reviewer comments on GitHub pull requests.

Community
Advanced
chroniicallydiistractedchroniicallydiistracted

source-command-review-pull-request

Review unanswered GitHub Pull Request comment threads and apply changes.

Community
Advanced
vercel-labsvercel-labs
5.8k

code-review

Analyze code changes and provide actionable feedback on defects, style, and design.

Official
Intermediate
lv7devlv7dev

code-review

Enforce technical rigor in code reviews with verification gates.

Community
Basic