vc-review

Generate structured artifacts and findings-max audits for PR reviews.

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/VetCoders/vibecrafted --skill vc-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-review
Source: https://github.com/VetCoders/vibecrafted/tree/main/skills/vc-review
Command: npx skills add https://github.com/VetCoders/vibecrafted --skill vc-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end PR review by generating structured artifacts and a comprehensive findings-max audit, replacing manual, ad-hoc reviews.

Core Features & Use Cases

  • Phase 1 artifact generation using prview-rs for current branches or GitHub PRs
  • Phase 2 findings-max audit with evidence-rich findings and before-merge TODOs
  • Output: machine-readable reports plus human-readable summaries for quick merge decisions
  • Use Case: standardize PR reviews across teams and enable traceable gate decisions

Quick Start

Run prview on your branch to generate artifacts and start the findings-max audit.

Frequently Asked Questions about vc-review

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

FAQPage Schema
How do I automate PR review with structured findings and traceable evidence?

Automate PR review using a two-phase workflow: generate branch artifacts with prview-rs, then run a findings-max audit to produce machine-readable reports and before-merge TODOs for traceable merge decisions.

What's the best way to run pre-merge checks and branch analysis on a GitHub PR?

Pre-merge checks and branch analysis are executed by generating structured artifacts for the current branch or GitHub PR, followed by a comprehensive audit that yields evidence-rich findings and actionable task lists before merging.

Can I generate machine-readable reports and human-readable summaries for merge gate decisions?

Yes, the review process outputs both machine-readable reports for automated gate logic and human-readable summaries to provide developers with quick merge decisions and traceable audit evidence.

How does a findings-max audit improve code review over manual ad-hoc checks?

A findings-max audit replaces manual ad-hoc checks by standardizing PR reviews across teams, generating consistent structured artifacts and comprehensive findings with before-merge TODOs for reliable gate decisions.

Do I need any special dependencies to run prview-rs for artifact generation?

No special dependencies are required to run artifact generation and the findings-max audit, as the Skill operates independently without external component prerequisites to perform branch analysis.

When should I not use automated findings-max audits for branch analysis?

Automated findings-max audits are not suited for contexts lacking a defined merge gate workflow, as the process relies on generating structured artifacts and before-merge TODOs to standardize PR reviews.