skills.rest
luan-thnh
luan-thnhCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

code-review

Enforce evidence-based code review with verification before completion.

Updated Jan 31, 2026
Search Tags:#verification#subagent#quality-assurance#process#code-review#software-engineering
One-click install
npx skills add https://github.com/luan-thnh/hrm-auto-extension --skill code-review-luan-thnh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/luan-thnh/hrm-auto-extension/tree/main/.opencode/skills/code-review
Command: npx skills add https://github.com/luan-thnh/hrm-auto-extension --skill code-review-luan-thnh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Code reviews often devolve into performative agreement or vague feedback. This skill establishes a rigorous, evidence-based approach that prioritizes technical correctness and verifiable outcomes.

Core Features & Use Cases

  • Receiving feedback: Evaluate feedback with a technical lens, verify relevance, and avoid blind agreement.
  • Requesting reviews: Trigger a dedicated code-reviewer subagent to obtain formal critique before progress.
  • Verification gates: Require fresh verification evidence (tests, builds, diffs) before claiming completion or status changes.

Quick Start

Submit your change and trigger a code-review to verify correctness before declaring completion.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I prevent performative agreement during code reviews?▼

An evidence-based code review protocol prevents performative agreement by enforcing technical evaluation of feedback and requiring fresh verification evidence before claiming task completion.

What is a verification gate in software engineering?▼

A verification gate in software engineering requires fresh verification evidence, such as tests, builds, or diffs, before allowing a developer to claim task completion or progress to a pre-merge workflow.

How do I dispatch a code-reviewer subagent for post-task completion?▼

You can dispatch a code-reviewer subagent by triggering a formal review request after post-task completion, ensuring a dedicated agent provides rigorous critique before any progress or merge is declared.

Can I use an evidence-based code review process for pre-merge workflows?▼

Yes, you can apply an evidence-based code review process to pre-merge workflows by enforcing a three-part protocol that receives feedback rigorously, requests reviews via subagent, and verifies completion with fresh evidence.

Why does my code review process produce vague feedback?▼

Code review processes produce vague feedback when they lack an evidence-based protocol, allowing performative agreement instead of enforcing technical rigor and verifiable outcomes through formal subagent-driven verification.

Related Skills

Explore More Software Engineering Skills→
novskidevnovskidev
2

receiving-code-review

Coordinates a structured 6-step response to code review feedback.

Community
Advanced
dobrinz123dobrinz123

gsd-ship

Push branches, create pull requests, and monitor merge status.

Community
Intermediate
HashWarlockHashWarlock
36

nobody-receives-code-review

Evaluate code review feedback with technical verification and evidence-based responses.

Community
Basic
SungmasterSungmaster

requesting-code-review

Dispatch a code reviewer subagent to evaluate changes against requirements.

Community
Intermediate