code-review

Process code review feedback with structured verification gates before completion.

Updated Dec 23, 2025

Search Tags:#feedback #verification #subagent #best-practices #code-review #pull-request

Ready to run

npx skills add https://github.com/dige04/hieu-ccsetup --skill code-review-dige04

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/dige04/hieu-ccsetup/tree/main/config/skills/code-review
Command: npx skills add https://github.com/dige04/hieu-ccsetup --skill code-review-dige04

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Handles code review feedback with technical rigor, ensuring verification before status claims and preventing performative agreement.

Core Features & Use Cases

Receiving feedback with a structured protocol to clarify items and verify implications.
Requesting reviews via a code-reviewer subagent to obtain independent validation.
Verification gates that require fresh evidence (tests/builds) before declaring completion.

Quick Start

Describe the changes and request a formal review to start the code-review process now.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I handle code review feedback without just agreeing to every suggestion?▼

Handling code review feedback without performative agreement requires a structured protocol to clarify items, verify technical implications, and demand fresh evidence like passing tests before declaring completion.

What is the best way to verify code changes before a pull request merge?▼

The best way to verify code changes before a pull request merge is applying strict verification gates that require fresh evidence from successful test runs and builds to validate status claims and prevent false completion declarations.

How do I request an independent code review using a subagent?▼

To request an independent code review using a subagent, describe your changes and trigger a formal review request to obtain independent validation from a dedicated code-reviewer subagent.

Does this code review process work for major feature development and bug fixes?▼

Yes, this code review process works for major feature development and bug fixes by enforcing technical rigor, structured feedback reception, and strict verification gates before any status claims are made.

When should I not use performative agreement in pull request reviews?▼

You should never use performative agreement in pull request reviews when handling complex feedback, as it bypasses technical rigor and skips the verification gates needed to ensure code accuracy before completion.