skills.rest
vuminhieu
vuminhieuCOMMUNITY
Explore all skills by this author →
GitHub

code-review

Evaluate code review feedback and enforce verification gates before completion.

Updated Feb 2, 2026
Search Tags:#verification#subagent#quality-assurance#code-review#evidence-based#pull-request
One-click install
npx skills add https://github.com/vuminhieu/spexor-client --skill code-review-vuminhieu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/vuminhieu/spexor-client/tree/main/.agent/skills/skills/code-review
Command: npx skills add https://github.com/vuminhieu/spexor-client --skill code-review-vuminhieu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures rigorous, evidence-based handling of code review feedback, preventing performative agreement and unverified claims by enforcing structured evaluation and verification before any completion statements.

Core Features & Use Cases

  • Feedback evaluation: Analyze comments for technical validity, prioritize items, and avoid performative praise.
  • Review coordination: Trigger and manage a code-reviewer subagent to solicit independent validation.
  • Verification gates: Require fresh evidence (tests, builds, diffs) before claiming success or progress.
  • Use Case: Before merging a major feature, run the review protocol to ensure all changes are justified and verifiable.

Quick Start

Initiate a review when you receive feedback on a patch, then follow the three-step cycle: read, verify, respond, and implement items one by one.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I enforce evidence-based code review feedback before merging a pull request?▼

Evidence-based code review feedback is enforced by applying structured evaluation, dispatching a code-reviewer subagent for independent validation, and requiring fresh verification like tests or builds before claiming completion.

What is the best way to prevent performative agreement during code reviews?▼

To prevent performative agreement during code reviews, enforce structured evaluation that analyzes comments for technical validity, prioritizes items, and requires fresh evidence such as diffs and builds before accepting any changes.

How does a code-reviewer subagent handle verification gates?▼

A code-reviewer subagent handles verification gates by requiring fresh evidence, including tests, builds, and diffs, to ensure traceable validation and disciplined governance before any completion statements are made.

How do I implement a structured code review cycle for patch feedback?▼

Implement a structured code review cycle by reading feedback, verifying comments, responding, and implementing items one by one while coordinating with a code-reviewer subagent to solicit independent validation.

When do I need to run a code review protocol using a subagent?▼

You need to run a code review protocol using a subagent before merging a major feature, ensuring all changes are justified, traceable, and verifiable through structured evaluation and evidence-driven checks.

Related Skills

Explore More Software Engineering Skills→
OneKeyHQOneKeyHQ
2.4k

pr-review

Review pull request diffs for security risks and vulnerabilities.

Official
Advanced
yocxy2yocxy2

land-and-deploy

Merge pull requests and verify production deployment health with canary checks.

Community
Advanced
ajsai47ajsai47
11

verification-before-completion

Require fresh verification evidence before claiming code completion or fixes.

Community
Intermediate
aivos-xieaivos-xie
1

requesting-code-review

Automate pre-commit code review with security scans and quality checks.

Community
Advanced