code-review

Dispatch a code-reviewer subagent to verify tests, builds, and evidence before completion claims.

3|1|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/vibery-studio/templates --skill code-review-vibery-studio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/vibery-studio/templates/tree/main/skills/code-review
Command: npx skills add https://github.com/vibery-studio/templates --skill code-review-vibery-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures technical rigor in code reviews by guiding how to receive feedback, request reviews through a subagent, and enforce verification gates before any status claims.

Core Features & Use Cases

  • Receiving Feedback Protocol to prevent performative agreement and ensure requirements are clarified
  • Requesting Review Protocol to dispatch a code-reviewer subagent after each task or major milestone
  • Verification Gates to validate tests, builds, and evidence before claiming completion or progress
  • References to detailed protocols in references/

Quick Start

Outline what you implemented and trigger a code-reviewer check before proceeding.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate code review for pull requests before merging?

To automate code review for pull requests, dispatch a code-reviewer subagent to gather feedback and validate changes. This enforces verification gates, ensuring tests, builds, and compliance checks pass before claiming completion.

What is evidence-based code review and when do I need it?

Evidence-based code review requires documented verification of tests, builds, and compliance checks before approving changes. You need it for pre-merge verification to prevent premature completion claims and ensure traceable approvals in software engineering.

How do I prevent performative agreement when receiving code review feedback?

Prevent performative agreement during code review by applying a receiving feedback protocol that clarifies requirements. This structured approach ensures technical rigor by demanding verifiable evidence and traceable approvals rather than superficial acknowledgments.

Can I use subagent-driven development workflows for quality assurance?

Yes, subagent-driven development workflows support quality assurance by dispatching a code-reviewer subagent after major milestones. This enforces verification gates to validate tests and builds, providing documented evidence before progress is claimed.

What are the limitations of automated code review in software engineering?

Automated code review limitations include its strict requirement for documented verification steps before completion. It enforces verification gates rather than providing creative architectural feedback, focusing purely on traceable approvals and pre-merge validation for existing changes.