skills.rest
vTRKA
vTRKACOMMUNITY
Explore all skills by this author →
GitHub

pre-pr-check

Verify pull request diffs against intent and produce evidence bundles.

Updated Apr 27, 2026
Search Tags:#code review#pull request#verification#residual risk#release readiness#evidence bundle#artifact links
One-click install
npx skills add https://github.com/vTRKA/supervibe --skill pre-pr-check-vtrka
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pre-pr-check
Source: https://github.com/vTRKA/supervibe/tree/main/skills/pre-pr-check
Command: npx skills add https://github.com/vTRKA/supervibe --skill pre-pr-check-vtrka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-review verification often becomes a guessing game: reviewers have to reconstruct intent, scope, and residual risk from incomplete context, which can slow approvals or hide regressions.

Core Features & Use Cases

  • Evidence-bundle preflight for PRs: validates that the diff matches stated intent, includes the required checks, and links durable artifacts for reviewer confidence.
  • Scoped verification from changed surfaces: targets checks to only the affected code, docs, prompts/skills, migrations, UI/browser behavior, and project-mandated gates.
  • Residual-risk and reviewer-readiness output: produces a reviewer-ready summary including what was verified, what was skipped, why, and who owns the next safe action.

Quick Start

Run this as the last engineering check before requesting review or merge by having the AI perform the pre-PR verification for your current diff and emit the READY/BLOCKED status plus an evidence bundle.

Frequently Asked Questions about pre-pr-check

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

FAQPage Schema
How do I prove pull request readiness with scoped evidence before review?▼

A pre-PR check proves readiness by inventorying the diff, running targeted checks on changed surfaces, validating artifact links, and emitting a structured READY status with a reviewer-ready evidence bundle before merge.

What is residual risk output in code review verification?▼

Residual risk output documents what was verified, skipped, and why, assigning ownership for the next safe action. This gives reviewers a clear summary of lingering issues before approving a merge.

How do I generate a reviewer-ready evidence bundle for a release candidate handoff?▼

Generate an evidence bundle by validating the diff matches intent, includes required preservation checks, and links durable artifacts. The process blocks completion if evidence is missing or stale, ensuring safe release-candidate handoffs.

Can I scope automated checks to only changed code surfaces for a pull request?▼

Yes, you can scope checks to only changed code surfaces, including affected docs, prompts, migrations, and UI behavior. Targeted verification runs project-mandated gates relevant to the specific diff.

What happens when artifact or receipt links are missing during pre-merge gate verification?▼

When artifact or receipt links are missing during pre-merge gate verification, the system blocks completion. It requires durable receipts and explicit residual risk to be present before allowing a merge.

Related Skills

Explore More Legal & Compliance Skills→
ksciuskscius
2

differential-review

Identify security-relevant changes in git diffs and generate a structured review report.

Community
Intermediate
s3nex-coms3nex-com

pr-merge-orchestrator

Coordinate pull request lifecycle from review through merge with mandatory gates.

Community
Advanced
KrismithReddy12KrismithReddy12

health

Calculate a weighted 0-10 code quality score from linters and test runners.

Community
Advanced
CarlosQ96CarlosQ96

launch-checklist

Generate a cross-department launch readiness checklist for game development projects.

Community
Advanced