Feature Map
VibePro is broader than a PR helper. It is an evidence control plane for AI-driven repository work: it keeps the story, specification, verification, reviews, and PR gate state connected.
Where it sits
VibePro is a CLI between AI agents and GitHub PRs. Codex or Claude Code creates the change; VibePro checks the Story, Spec, verification, reviews, and PR readiness for that change.
CI/CD, release procedures, and hosting infrastructure come after VibePro. VibePro does not host or run the application. It checks whether the change has the intent, verification, review, and PR evidence needed before it moves downstream.
Main capability areas
| Area | What it answers | Start with |
|---|---|---|
| PR readiness | Can this change become a PR now? | vibepro pr prepare |
| Gate DAG | Which requirements are blocking the PR path? | vibepro check pr-readiness |
| Story and Spec | What is the intended change, and what behavior must hold? | vibepro story status, vibepro spec show |
| Traceability | Which acceptance criteria connect to code, tests, and PR evidence? | vibepro trace backfill |
| Verification | What was actually run against the current git state? | vibepro verify record |
| Agent Review | Which required review roles have passed, changed, or blocked? | vibepro review status |
| Check Packs | Which risk surface should be checked now? | vibepro check <pack> |
| Graphify context | What code graph context should inform impact scope? | vibepro graph . --run-graphify |
| Design System | Are UI changes aligned with local product rules? | vibepro design-system validate |
| Journey and flow | Which user path does the change affect? | vibepro journey derive, vibepro verify flow |
| Performance | Is speed a first-class acceptance condition? | vibepro performance define |
| Execution | How is multi-step work tracked before and after PR creation? | vibepro execute status |
| Harness and learning | What patterns should be promoted into future checks or skills? | vibepro usage report, vibepro harness review-learnings |
A practical reading order
For a first run, read the manual in this order:
- AI PR Workflow
- Gates and Evidence
- Graphify Impact Context
- Story, Spec, and Traceability
- Check Packs
- Verification, Decisions, and CI Evidence
- Checkpoints and Execution
Use the reference pages when you need exact command forms or artifact locations.