ship

To automate git workflow verification before a pull request, coordinate end-to-end ship operations by running a consolidated verification gate for type checks, standards checks, tests, and builds in a merged state to ensure changes are validated before landing.

A pre-flight check in a code review and ship workflow is a baseline sync and validation step to ensure your feature branch is ready. It prevents landing on red baselines or unbumped schemas before proceeding with PR creation.

You can auto-generate a PR body for a feature branch by running an automated ship workflow that creates the pull request after passing all verification gates. The workflow automatically generates the body and prompts for any missing capability entries.

Yes, you can enforce code review checks and tests in a merged state before opening a PR. A consolidated verification gate runs typecheck, standards, docs, tests, and builds against the merged state to validate changes before pull request creation.

Preventing a merge on a red baseline acts as a guardrail to avoid landing broken code, but it requires the baseline to be fully green before shipping. You must sync and resolve any failing checks on the baseline branch before proceeding with the PR.