vibepro-diagnosis-packageslisted

# VibePro Diagnosis Packages ## Purpose Use VibePro purpose-level packages instead of guessing which low-level scanner or log to inspect. The package is the user-facing intent; the scanner set and evidence paths are VibePro's implementation detail. ## When to Use Use this Skill when the user asks VibePro to check, audit, diagnose, verify, or compare UI behavior, security, performance, architecture, PR readiness, launch readiness, agent harness readiness, public discovery, self-dogfood readiness, OSS readiness, or regression risk. Use it when a claim needs package-level evidence rather than ad hoc scanner output, especially when the user asks whether VibePro has "confirmed" something. ## Diagnosis Packages List packages first when the request is ambiguous: ```bash vibepro check list ``` Use these mappings: - UI quality / user flow / API contract in UI calls / gesture UX: `vibepro check ui <repo> --story-id <story-id>` - Security / auth / exposed surface / API route contracts: `vibepro check security <repo> --story-id <story-id>` - Performance readiness / heavy dev / DB access risks: `vibepro check performance <repo> --story-id <story-id>` - Architecture / responsibility boundary: `vibepro check architecture <repo> --story-id <story-id>` - PR readiness: `vibepro check pr-readiness <repo> --story-id <story-id> --base <ref> --head <ref>` - Release or handoff readiness: `vibepro check launch-readiness <repo> --story-id <story-id>` - Broad inspection: `vibepro check all <