vv-review

Routes code and specification review requests to specialized sub-agents and returns severity-tagged findings.

11|1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/osovv/vv-opencode --skill vv-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vv-review
Source: https://github.com/osovv/vv-opencode/tree/main/templates/skills/vv-review
Command: npx skills add https://github.com/osovv/vv-opencode --skill vv-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually coordinating code and specification reviews is time-consuming, inconsistent, and often leads to missed issues or unvetted fixes being implemented prematurely. This Skill automates the entire review workflow, ensuring the right specialized reviewers are engaged, all required review scopes are covered, and findings are delivered in a structured format without jumping to unapproved fixes.

Core Features & Use Cases

  • Automated Review Routing: Automatically selects the appropriate reviewer sub-agents (spec-focused, code-focused, or both) based on the type of review request.
  • Structured Finding Reports: Compiles review results with clear severity levels, exact file locations, and actionable fix direction for easy triage and team alignment.
  • Use Case: Use this Skill when validating a new feature implementation against its acceptance criteria, checking recent code changes for security vulnerabilities and regressions, or completing a full compliance review before merging a pull request.

Quick Start

Use the vv-review skill to run a full code and spec review of the recent authentication feature changes and get a structured list of all findings.

Frequently Asked Questions about vv-review

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

FAQPage Schema
How do I automate pull request review workflows to catch security vulnerabilities and regressions?

Automating code review workflows involves routing requests to specialized sub-agents to validate specifications and detect security vulnerabilities. This process delivers severity-tagged, structured findings reports without implementing unapproved fixes.

What is the best way to validate new feature implementation against acceptance criteria?

Validating feature implementations against acceptance criteria requires routing review requests to spec-focused sub-agents. This generates structured findings reports with severity levels and exact file locations for easy triage.

How do I generate a structured findings report for maintainability assessments without applying fixes?

Generating a structured findings report for maintainability assessments requires a review-only workflow that delivers severity-tagged issues. This maintains review integrity by providing actionable fix directions without implementing unapproved code changes.

Does automated code review routing support both specification validation and bug detection simultaneously?

Automated code review routing supports both specification validation and bug detection by selecting appropriate reviewer sub-agents based on the request type. It coordinates spec-focused and code-focused reviews to cover all required scopes.

When should I use a review-only workflow for software development compliance checks?

Use a review-only workflow for compliance checks when you need severity-tagged findings for maintainability and security audits before merging pull requests. This prevents unvetted fixes from being implemented prematurely during the review process.

Why does automated spec review deliver findings instead of directly patching the code?

Automated spec review delivers findings instead of patching code to maintain review integrity and prevent unvetted fixes. This ensures teams can triage severity-tagged issues and align on actionable fix directions before implementation.