requesting-code-review

Convert PR candidates into evidence-backed review packets with scope and risk context.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/vTRKA/supervibe --skill requesting-code-review-vtrka
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/vTRKA/supervibe/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/vTRKA/supervibe --skill requesting-code-review-vtrka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents unclear, evidence-poor pull requests and plan reviews by turning a change into a reviewer-ready handoff with scope, diff intent, verification receipts, and risk context.

Core Features & Use Cases

  • Evidence-backed review packet: bundles scope packet, per-file diff summary, verification evidence (including exact commands/exit codes), known risks, and reviewer selection rationale.
  • Reviewer gate for high-stakes changes: supports strict plan-review mode and enforces required baseline reviewer coverage plus risk-triggered specialists when needed.
  • Operational safety and completeness checks: blocks review invocation if required fields (scope packet, diff summary, verification evidence, known risks, reviewer selection) or required receipts/artifacts are missing.
  • Reviewer prompt standardization: instructs the reviewer to use the durable reviewer-output template with consistent severity, line-level findings, impact, evidence, and verdict.

Quick Start

Ask your AI tool to run requesting-code-review before opening or sending a PR by providing the plan/PR candidate and the evidence/verification artifacts needed for a review loop.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I package a pull request with verification evidence for code review?

Package a pull request with verification evidence by converting implemented work into a reviewer-ready review packet containing scope, per-file diff summary, verification receipts, and risk context.

What is a review packet and how does it improve code review gating?

A review packet is an evidence-backed handoff artifact that improves code review gating by bundling diff intent, verification evidence, known risks, and reviewer selection rationale to prevent unclear pull requests.

How do I enforce reviewer coverage rules for high-stakes plan review?

Enforce reviewer coverage rules for high-stakes plan review by applying strict plan-review mode to require baseline reviewer coverage and trigger risk-specific specialists before completion.

Can I block code review invocation if required verification receipts are missing?

Yes, you can block code review invocation if required verification receipts are missing; the operational safety checks prevent invocation when scope packets, diff summaries, or risk artifacts are incomplete.

What is the best way to standardize reviewer output for a code review?

Standardize reviewer output for a code review by instructing reviewers to use a durable template with consistent severity, line-level findings, impact, evidence, and verdict fields.

When should I not use an evidence-backed review packet?

You should not use an evidence-backed review packet for trivial changes that do not require scope definition, risk assessment, or formal reviewer handoff artifacts.