receiving-code-review

Name: receiving-code-review
Availability: InStock
Author: sheer-rey

Evaluate code review feedback for technical validity before implementation.

Updated Sep 27, 2024

Search Tags:#git #code review #feedback #collaboration #validation #pull requests

Ready to run

npx skills add https://github.com/sheer-rey/PowerBash --skill receiving-code-review-sheer-rey

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/sheer-rey/PowerBash/tree/main/.claude/skills/receiving-code-review
Command: npx skills add https://github.com/sheer-rey/PowerBash --skill receiving-code-review-sheer-rey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you respond to code review feedback with technical rigor instead of reflexive agreement, so you can avoid implementing unclear or incorrect suggestions.

Core Features & Use Cases

Feedback Verification: Checks review comments against the actual codebase before any change is made.
Clarification First: Prompts for missing details when a review request is ambiguous, incomplete, or overlapping.
Reasoned Pushback: Gives you a framework for rejecting suggestions that would break behavior, conflict with architecture, or violate YAGNI.
Safe Implementation Order: Encourages fixing blocking issues first, then simpler changes, then larger refactors, with testing after each step.

Quick Start

Use this skill to evaluate the latest code review comments and tell me which suggestions are valid, which need clarification, and which should be challenged with technical reasons.

Frequently Asked Questions about receiving-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I validate code review feedback before implementing changes?▼

Evaluate code review feedback against the actual codebase to determine if suggestions are technically valid, unclear, or harmful before making any modifications. This ensures technically rigorous responses and prevents implementing incorrect or ambiguous suggestions.

How should I respond to unclear pull request comments?▼

Respond to unclear pull request comments by prompting the reviewer for missing details and clarification before attempting any implementation. This clarification-first workflow resolves ambiguity and overlapping requests, ensuring you fully understand the required change before writing code.

What is the best way to push back on code review suggestions that break behavior?▼

The best way to push back on harmful code review suggestions is to provide reasoned technical objections explaining why the change would break behavior, conflict with architecture, or violate YAGNI. This framework justifies rejection with technical rigor instead of reflexive agreement.

What order should I implement code review changes in a pull request?▼

Implement code review changes by fixing blocking issues first, then applying simpler changes, and finally executing larger refactors. Test the codebase after each step to ensure safe implementation and verify that incremental changes do not introduce new behavior regressions.

Can I use this approach for inline PR comments and reviewer disagreements?▼

Yes, this validation approach applies directly to pull request review responses, inline comment handling, and reviewer disagreement workflows. It helps manage collaborative feedback by requiring careful validation and reasoned pushback during software development collaboration.