AI PR Workflow

The normal VibePro workflow keeps PR creation behind evidence.

1. Define or choose a story

Use vibepro init for a known feature or bug.

vibepro init /path/to/repo \
  --story-id story-<short-name> \
  --title "<title>" \
  --language en

If stories already exist, list or map them before choosing one.

vibepro story list /path/to/repo
vibepro story map /path/to/repo

2. Diagnose before implementation

Run a broad check when the repository or story is unfamiliar.

vibepro check all /path/to/repo \
  --story-id <story-id> \
  --base <base-branch>

Use focused checks for specific risks:

vibepro check ui /path/to/repo --story-id <story-id>
vibepro check security /path/to/repo --story-id <story-id>
vibepro check performance /path/to/repo --story-id <story-id>
vibepro check architecture /path/to/repo --story-id <story-id>
vibepro check pr-readiness /path/to/repo --story-id <story-id> --base <base-branch>

3. Prepare PR evidence

Run pr prepare after implementation changes exist.

vibepro pr prepare /path/to/repo \
  --base <base-branch> \
  --story-id <story-id>

The command classifies the change, builds PR artifacts, and prints next commands. If required gates are unresolved, the next command should point back to review, verification, or preparation rather than PR creation.

4. Record evidence

Record what actually ran.

vibepro verify record /path/to/repo \
  --id <story-id> \
  --kind typecheck \
  --status pass \
  --command "npm run typecheck"

If a command cannot run, record the true status instead of inventing a pass.

5. Use VibePro's PR path

When ready:

vibepro pr create /path/to/repo \
  --base <base-branch> \
  --head <branch> \
  --story-id <story-id>

For a dry-run readiness check:

vibepro pr ship /path/to/repo \
  --base <base-branch> \
  --head <branch> \
  --story-id <story-id> \
  --dry-run