receiving-code-review

Verify code review feedback against the codebase before implementation.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Jhabbig/Habbig --skill receiving-code-review-jhabbig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/Jhabbig/Habbig/tree/main/.claude/skills/receiving-code-review
Command: npx skills add https://github.com/Jhabbig/Habbig --skill receiving-code-review-jhabbig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Feedback Verification: Restates review comments in technical terms and checks them against the actual codebase.
  • Clarification and Pushback: Identifies ambiguous items, asks for clarification, and pushes back when suggestions conflict with current behavior or architecture.
  • Incremental Implementation: Supports one-item-at-a-time changes with verification after each step, which is especially useful for multi-comment review threads and external reviewer feedback.

Quick Start

Use the receiving-code-review skill to evaluate this review feedback, verify whether each suggestion is technically correct for the current codebase, and tell me what should be implemented first.

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 if code review feedback is technically correct before implementing it?

Verify code review feedback by restating comments in technical terms and checking them against the actual codebase. This process evaluates suggestions issue-by-issue to ensure they align with existing architecture before you make any edits.

What is the best way to handle ambiguous change requests in a multi-comment review thread?

Handle ambiguous change requests by evaluating the review thread one item at a time. You identify unclear items, ask for clarification, and apply reasoned pushback when suggestions conflict with current behavior or architecture.

Can I push back on external reviewer feedback that conflicts with my codebase architecture?

Yes, you can push back on external reviewer feedback. When review comments conflict with current behavior or architecture, you restate the feedback technically and provide reasoned pushback instead of reflexively implementing the suggested changes.

How do I implement multiple code review changes without breaking existing behavior?

Implement multiple code review changes incrementally, one item at a time. Verify the codebase after each step to ensure existing behavior and architecture remain intact throughout the feedback implementation process.

When do I need technical validation for code review comments?

You need technical validation for code review comments when dealing with external reviewer feedback, ambiguous change requests, or multi-item threads. This validation ensures suggestions are technically correct for the current codebase before edits begin.