address-feedback

Verify code-review feedback against the codebase before applying changes.

Updated Mar 21, 2026

Search Tags:#workflow #feedback #verification #quality #evidence #engineering #code-review

Ready to run

npx skills add https://github.com/monkerek/vibe-hub --skill address-feedback

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: address-feedback
Source: https://github.com/monkerek/vibe-hub/tree/main/.vibe/skills/address-feedback
Command: npx skills add https://github.com/monkerek/vibe-hub --skill address-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill governs how AI agents receive and act on code review feedback. It replaces reflexive compliance ("You're absolutely right!") with a rigorous verify-then-implement workflow. Every piece of feedback is treated as a technical hypothesis to evaluate — not an order to obey.

Core Features & Use Cases

Verify-before-implement workflow with a HARD-GATE that requires verification against the codebase before applying changes.
Evidence-based verification using tool outputs to justify every modification.
One-item-at-a-time execution to minimize regressions and improve traceability.

Quick Start

Review and address each code-review item with evidence-based verification before applying changes.

Frequently Asked Questions about address-feedback

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

FAQPage Schema

How do I address code review feedback without blindly applying changes?▼

To address code review feedback safely, you should verify every item against the actual codebase before implementation. This approach treats feedback as a technical hypothesis to evaluate rather than an order to obey, preventing performative agreement and ensuring correctness.

What is the verify-before-implement workflow for code review?▼

The verify-before-implement workflow uses a hard gate that requires validating code review feedback against the codebase using tool outputs. It ensures evidence-based verification justifies every modification before execution, replacing reflexive compliance with rigorous evaluation.

How to apply code review feedback one item at a time?▼

Applying code review feedback one item at a time involves validating each change with tool outputs before moving to the next. This one-item-at-a-time execution minimizes regressions and improves traceability by ensuring every modification is verified against the codebase.

Why does an AI agent agree with code review feedback but break the code?▼

AI agents often break code due to reflexive compliance, where changes are implemented solely for appearance or performative agreement. Replacing this with evidence-based verification ensures every modification is validated against the codebase to prevent regressions from unverified feedback.

Can I use evidence-based verification to justify code review modifications?▼

Yes, evidence-based verification uses tool outputs to justify every code modification made during a code review. By verifying each feedback item against the codebase, you provide concrete evidence for decisions and avoid implementing changes based solely on appearance.