review-and-ship

To automate code review and pull request readiness, the Skill validates feature branches against tests and PR rules. It gathers context, runs targeted tests, applies deterministic checks, and ensures changes align with intent before pushing or opening PRs.

The best way to verify bugfix changes before opening a PR is to run selective, targeted tests against the code diff. The Skill coordinates this by enforcing deterministic checks on the specific changes, ensuring test coverage and intent alignment before pushing updates.

Yes, you can use this for pre-merge validation workflows to craft selective commits. The Skill automates the end-to-end review process by enforcing deterministic checks, creating concise focused commits, and coordinating reviewer feedback before final PR creation.

No external dependencies are required to validate code changes. The Skill operates independently across a typical Git workflow, coordinating tests, diffs, and reviewer feedback natively to enforce PR readiness and governance for feature branches and bugfixes.

You should not use an automated review and ship workflow if your code changes require manual, non-deterministic validation logic outside of standard Git workflows. The Skill enforces deterministic checks and relies on targeted tests, making it unsuitable for unscripted validation scenarios.