handle-review

Verify code review feedback for technical accuracy before implementation.

Updated Feb 22, 2026

Search Tags:#code review #feedback #implementation #verification #technical rigor #pushback

Ready to run

npx skills add https://github.com/jpeggdev/buildwithjpegg --skill handle-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: handle-review
Source: https://github.com/jpeggdev/buildwithjpegg/tree/main/plugins/development-workflow/skills/handle-review
Command: npx skills add https://github.com/jpeggdev/buildwithjpegg --skill handle-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the common pitfall of blindly accepting code review feedback, ensuring technical rigor and verification before implementation to prevent errors and maintain code quality.

Core Features & Use Cases

Structured Response Pattern: Guides users through a 6-step process for handling feedback, emphasizing understanding and verification.
Distinguishes Feedback Sources: Provides specific verification steps for feedback from human partners versus external reviewers.
Use Case: When a reviewer suggests a change, this skill prompts you to verify its technical correctness and impact on the codebase before making any modifications, preventing the introduction of new bugs or the removal of necessary functionality.

Quick Start

When receiving code review feedback, verify its technical soundness against the codebase before implementing any suggestions.

Frequently Asked Questions about handle-review

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

FAQPage Schema

How do I verify code review feedback before implementation?▼

To verify code review feedback before implementation, follow a structured 6-step response pattern that prioritizes understanding, technical verification, and reasoned pushback over performative agreement. This ensures technical accuracy and prevents errors.

Why does blindly accepting code review feedback cause problems?▼

Blindly accepting code review feedback causes problems by introducing new bugs or removing necessary functionality. It skips technical verification, leading to errors and degrading overall code quality in the project.

How do I handle feedback from external reviewers versus human partners?▼

Handling feedback from external reviewers versus human partners requires distinguishing the feedback sources. The process applies specific verification steps for each source to ensure adherence to project requirements and technical correctness.

Can I push back on code review suggestions if they are technically incorrect?▼

You can push back on code review suggestions if they are technically incorrect. The process enforces reasoned pushback over performative agreement, prompting you to verify technical soundness and codebase impact before making modifications.

What is the best way to manage code review feedback for technical rigor?▼

The best way to manage code review feedback for technical rigor is applying a strict verification process before implementation. This prevents performative agreement and ensures all suggested changes align with project requirements.

When should I not use performative agreement during code review?▼

You should not use performative agreement during code review when receiving feedback from human partners or external reviewers. Instead, prioritize understanding and verification to maintain technical accuracy and codebase integrity.