Check Packs

Check packs let you run the right gate family for the current risk surface. all exists, but targeted packs are usually faster and easier to interpret.

Available packs

Pack	Use when	Main surfaces
ui	visual behavior, interaction, or route flow changes	component style, flow design, gestures, network and terminal-link contracts
security	auth, secrets, static hosting, or API boundaries are touched	static site, API boundary, network contracts, code quality
performance	runtime speed, local startup, queries, or resource use matters	database access, local dev, code quality
architecture	module boundaries, runtime contracts, or data access change	architecture profile, code quality, API boundary, database access
pr-readiness	you need the PR gate status	PR preparation
launch-readiness	a change is close to release	static site, API, network, UI, DB, local dev, code quality
agent-harness	agent workflow evidence or learning loop is in scope	agent harness
public-discovery	public documentation or AI-search visibility matters	public discovery
self-dogfood	VibePro is checking its own workflow	self-dogfood readiness
oss-readiness	package or repository is being prepared for open source release	OSS readiness
regression-risk	a small change may have broad blast radius	regression risk
all	you need a broad local sweep	core checks across the repository

Common commands

vibepro check pr-readiness . --story-id <story-id> --base origin/main
vibepro check architecture . --story-id <story-id> --base origin/main --json
vibepro check launch-readiness . --story-id <story-id> --include-public-discovery

Use --fail-on-findings in CI only when the pack is expected to be enforcement-grade for that repository. During exploration, prefer reading the findings first.