review-and-ship

To validate a Git branch before a pull request, analyze the diff against the base branch to check for bugs, regressions, and test coverage gaps. This pre-PR workflow ensures changed files match the intended goals and pass targeted tests.

Run targeted tests for changed files by analyzing the branch diff to identify modified behavior. The workflow determines which specific tests to execute for those areas and decides whether to add missing tests or document the coverage gaps.

Yes, you can fix critical issues found during the diff analysis and commit changes selectively. This practical readiness workflow ensures only focused fixes are pushed, preventing unrelated modifications from contaminating the final pull request.

Assess CI readiness by executing `gh pr checks` after opening or updating the pull request. This validates that the continuous integration pipelines have passed, providing concrete evidence that the branch is ready for merging.

The best way to ensure a code review checks intent fit and security regressions is to combine diff analysis with recent commit context. This approach prioritizes correctness and security by validating whether the implementation matches the actual requirements.

You should avoid using an automated pre-PR validation workflow when your branch requires complex architectural discussions or manual subjective review that cannot be captured by diff analysis, targeted testing, or selective commit workflows.