code-review

Review code changes with structured feedback and verification gates.

1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/hoanghd218/tranvanhoang.com --skill code-review-hoanghd218
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/hoanghd218/tranvanhoang.com/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/hoanghd218/tranvanhoang.com --skill code-review-hoanghd218

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Code reviews often rely on performative agreement and unverified claims. This Skill enforces technical rigor by introducing structured feedback, verification gates, and explicit protocols to ensure changes are correctly implemented and backed by evidence.

Core Features & Use Cases

  • Receiving feedback protocol to evaluate suggestions without blind agreement.
  • Requesting reviews to invoke a code-reviewer subagent after tasks or major changes.
  • Verification gates to ensure tests/builds are green before claiming completion.
  • Guidance and references to standardize the review process across teams.

Quick Start

Start by triggering a code-review after each task, dispatch the code-reviewer subagent, and address feedback before merging.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I enforce verification gates before claiming task completion in code reviews?

Verification gates ensure tests and builds pass before claiming task completion. You trigger a code-review after implementing features, dispatch a code-reviewer subagent, and address feedback before merging to enforce technical rigor.

What is the best way to automate structured code reviews after implementing features?

The best way to automate structured code reviews is using a subagent-driven workflow that enforces receiving feedback, requesting reviews, and verification gates to ensure changes are correctly implemented and backed by evidence.

How does a subagent-driven code review workflow handle unverified claims?

A subagent-driven code review workflow handles unverified claims by enforcing technical rigor through structured feedback, verification gates, and explicit protocols, ensuring changes are correctly implemented and backed by evidence before completion.

Can I use reference files to standardize the code review process across teams?

Yes, you can use reference files to standardize the code review process across teams. These references guide responses and enforce receiving feedback, requesting reviews, and verification gates before merging code changes.

When do I need to request a code review using a subagent?

You need to request a code review using a subagent after implementing features, before creating PRs, and when claiming task completion. This ensures changes are correctly implemented and backed by evidence through verification gates.

How do I evaluate code review feedback without blind agreement?

To evaluate code review feedback without blind agreement, apply a receiving feedback protocol that enforces technical rigor through structured reviews, verification gates, and explicit protocols to ensure changes are correctly implemented.