code-review

Request code reviews from a subagent before merging changes.

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/Hoang130203/Emgu_CV_automation --skill code-review-hoang130203
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Hoang130203/Emgu_CV_automation/tree/main/.opencode/skills/code-review
Command: npx skills add https://github.com/Hoang130203/Emgu_CV_automation --skill code-review-hoang130203

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures code quality through rigorous technical review and verification, preventing errors and ensuring task completion claims are evidence-based.

Core Features & Use Cases

  • Technical Rigor: Prioritizes technical correctness over social comfort in feedback.
  • Systematic Review: Utilizes a dedicated subagent for code reviews before merging.
  • Verification Gates: Mandates evidence-based checks before any claim of completion or success.
  • Use Case: Before merging a feature, you can use this skill to request a review from a code-reviewer subagent, ensuring all requirements are met and no critical issues are overlooked.

Quick Start

Request a code review for your latest changes using the code-review skill.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I ensure my pull request passes technical verification before merging?

Technical verification before merging requires systematic code review processes that emphasize technical accuracy and evidence-based checks. You can request a dedicated subagent review to verify requirements are met and prevent premature success assertions.

What is the best way to automate quality assurance checks for a software development lifecycle?

Quality assurance automation in the software development lifecycle is achieved by implementing verification gates. These gates mandate evidence-based checks before any task completion claim, ensuring code correctness and preventing errors.

How do I get rigorous code review feedback without social bias?

Rigorous code review feedback without social bias is obtained by prioritizing technical correctness over social comfort. This approach ensures reviews focus strictly on technical accuracy and systematic verification of the code.

When do I need to use a subagent for code reviews?

You need to use a subagent for code reviews when you want to ensure all feature requirements are met and no critical issues are overlooked before merging. This dedicated subagent performs systematic verification of your latest changes.

Why does my code review process fail to catch critical issues before completion?

Code review processes fail to catch critical issues when they lack verification gates and technical rigor. Implementing evidence-based checks and systematic subagent reviews prevents premature success assertions and ensures all requirements are met.