What VibePro Is

VibePro is a CLI control plane for safer AI-driven pull requests.

It turns a feature story into architecture context, behavioral specification, verification evidence, agent-review evidence, and PR artifacts. It then blocks the normal VibePro PR creation path until the required gates are satisfied or explicitly waived.

How VibePro fits into a stack

VibePro is a local CLI run by a human or an AI coding agent in a repository where agents such as Codex or Claude Code are doing implementation work.

It is not a runtime plugin inside a hosting platform, CI/CD system, or application runtime. VibePro runs before PR creation in the local or agent work environment. It gathers the change intent, specification, verification results, review evidence, and PR artifact set before the team moves on to GitHub PR and its release process.

A typical setup looks like this:

In that stack, VibePro is the pre-PR evidence layer between AI-agent implementation work and the team's review and release process.

The problem it solves

AI coding agents can produce large changes quickly, but the risky part is often not code generation. The risky part is knowing whether the change still matches the intended product behavior, preserves architecture boundaries, covers important user flows, and has enough review evidence for a human to merge it.

VibePro makes that final stretch explicit.

What VibePro does

• Creates and reads repo-local story, spec, architecture, verification, and review artifacts.
• Builds risk-adaptive Gate DAGs for PR readiness.
• Records verification evidence against the current git state.
• Prepares agent-review requests and records completed review outcomes.
• Produces human-readable PR evidence such as pr-body.md, review-cockpit.html, gate-dag.html, and split-plan.html.
• Enforces the VibePro PR path so unresolved gates and waiver reasons are visible.

What VibePro does not do

• It does not rewrite your application by itself.
• It does not replace tests, code review, or product judgment.
• It does not assume every repository uses the same base branch, deployment platform, or release workflow.
• It does not build, host, or monitor the application in place of CI/CD or hosting infrastructure.
• It does not treat a green typecheck as proof that a workflow-heavy product change is ready.

Who should use it

VibePro is meant for engineers and AI coding agents working on repositories where PR quality depends on more than a diff. It is designed for teams that implement with Codex or Claude Code, review through GitHub PRs, and release through their existing CI/CD or operations process. It is especially useful when a change touches user journeys, runtime behavior, API contracts, design systems, verification evidence, or review orchestration.