receiving-code-review

Verify code review feedback against the codebase before implementing suggestions.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/Envy-7z/mobile-agent-skillpack --skill receiving-code-review-envy-7z
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/Envy-7z/mobile-agent-skillpack/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/Envy-7z/mobile-agent-skillpack --skill receiving-code-review-envy-7z

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the common pitfall of blindly implementing code review feedback without proper technical verification, preventing the introduction of errors or unnecessary changes.

Core Features & Use Cases

  • Verification First: Ensures all feedback is technically sound and relevant to the codebase before implementation.
  • Clarification Handling: Provides a structured way to ask for clarification on unclear feedback.
  • Reasoned Pushback: Enables graceful and technically grounded disagreement with feedback when necessary.
  • Use Case: When a reviewer suggests a change, this skill guides you to first check if the suggestion breaks existing functionality, aligns with project goals (YAGNI), and is technically correct for your specific stack, before writing any code.

Quick Start

When receiving code review feedback, verify each item against the codebase reality before responding or implementing.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I verify code review feedback before implementing changes?

Verify code review feedback by checking technical correctness, ensuring suggestions do not break existing functionality, and aligning changes with project goals like YAGNI before writing any code.

What is the best way to pushback on code review comments?

Pushback on code review comments requires reasoned disagreement, providing technically grounded justifications based on codebase reality and project-specific rules rather than performative agreement or unstructured refusal.

How do I ask for clarification on unclear code review feedback?

Handle unclear code review feedback by using a structured clarification process to request specific technical details from the reviewer, ensuring you understand the intent before modifying the codebase.

When should I not implement code review suggestions?

Avoid implementing code review suggestions when the feedback fails technical verification, introduces unnecessary changes violating YAGNI, or lacks sufficient clarity after requesting further explanation from the reviewer.