skills.rest
unclecatvn
unclecatvnCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

code-review

Review code changes with evidence-based verification before merging.

120|56|Updated Jan 16, 2026
Search Tags:#automation#feedback#verification#code-review#pull-request#technical-rigor
One-click install
npx skills add https://github.com/unclecatvn/agent-skills --skill code-review-unclecatvn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/unclecatvn/agent-skills/tree/main/skills/code-review
Command: npx skills add https://github.com/unclecatvn/agent-skills --skill code-review-unclecatvn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Code reviews often rely on social cues rather than rigorous technical validation. This skill enforces technical correctness and evidence-based assessment to avoid unclear feedback and premature completion.

Core Features & Use Cases

  • Receiving feedback with technical rigor over performative agreement
  • Requesting reviews via the code-reviewer subagent
  • Enforcing verification gates before status claims (tests, builds, and evidence)
  • Structured response patterns and escalation using the full protocol

Quick Start

Begin a code-review session by describing your changes and requesting a code-reviewer pass 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 technical rigor in code reviews instead of performative agreement?▼

Structured code reviews enforce technical rigor by applying evidence-backed assessment protocols. This replaces social cue validation with explicit verification gates, ensuring changes are technically validated through a structured READ-UNDERSTAND-VERIFY-EVALUATE-RESPOND-IMPLEMENT cycle before merging.

How do I verify code changes before claiming a pull request is ready to merge?▼

Verify changes before merging using explicit verification gates that require test passes, successful builds, and concrete evidence. This structured workflow prevents premature completion claims by enforcing technical validation steps before any status updates are made.

What is the best way to structure feedback when receiving a code review?▼

The best way to structure feedback is using a standardized response protocol that prioritizes evidence and technical correctness. This ensures assessments are clear, technically grounded, and avoid vague performative agreement during the review process.

Can I use a subagent to request automated code reviews for my pull request?▼

Yes, you can request reviews via a code-reviewer subagent. This subagent-driven workflow applies rigorous technical assessment and explicit verification gates to validate your pull request changes before allowing a merge status claim.

Does automated code review work without configuring explicit verification gates?▼

No, explicit verification gates are required to prevent premature completion. The review process depends on structured response protocols and evidence-based validation to ensure technical correctness, avoiding unclear feedback and unverified status claims.

Related Skills

Explore More Software Engineering Skills→
alexandersumeralexandersumer
1

review-deep

Generate candidate Reviewer evidence and validate code changes directly.

Community
Advanced
fredrikaverpilfredrikaverpil
253

code-review

Enforce evidence-based verification gates before claiming code review completion.

Community
Basic
Khoatran1999Khoatran1999

code-review

Evaluate code changes against evidence with verification gates before merging.

Community
Advanced
rafaelcallejarafaelcalleja
2

code-review

Guide structured code review feedback and verification in subagent-driven development.

Community
Basic