review-and-ship
Review the current branch for bugs, intent fit, and test coverage; run or write tests; commit focused work; open or update a PR.
Security Assessment
About review-and-ship
This skill defines a pre-ship review-and-release workflow for a coding agent working on a feature branch. It solves the problem of shipping changes without adequate verification by walking through gathering context, running or writing tests, reviewing the diff for correctness and regressions, fixing critical issues, committing focused work, and opening or updating a pull request. It is a concise, single-file skill from the Cursor team kit that codifies good release hygiene.
The workflow gathers the diff against the base branch, uncommitted changes, recent commits, and user intent; runs targeted tests for changed behavior (or documents the gap when none exist); reviews for correctness, regressions, security, and intent fit — suggesting parallel subagents for larger diffs; fixes critical issues and re-runs affected tests; commits selective files with a concise message; and pushes to open or update a PR. Suggested checks use standard read-oriented Git and GitHub CLI commands such as fetching the base branch, diffing, checking status, and querying PR check status with `gh pr checks`. Guardrails prioritize correctness and security over style-only comments, keep commits focused, and instruct fixing pre-commit failures rather than bypassing hooks.
The target users are software developers and teams who use an agentic coding assistant and want a repeatable, disciplined path from a finished branch to an open PR. It fits everyday feature development, bug-fix branches, and any workflow where reviewing before shipping and producing a clear findings summary matter.
FAQ
When should this skill be used?
When reviewing changes on the current branch before shipping — to verify behavior, run tests, commit focused work, and open or update a pull request.
What tools does it rely on?
Standard Git and the GitHub CLI (`gh`). Suggested checks include fetching the base branch, diffing against it, checking status, and using `gh pr checks` to judge PR readiness.
Does it bypass safety checks to ship faster?
No. A guardrail explicitly says that if pre-commit checks fail you should fix the issues rather than bypass hooks, and to prioritize correctness, security, and regressions over style-only comments.
What does it produce?
A findings summary categorized as critical, warning, and note; a record of tests run and their outcomes; and the URL of the opened or updated PR.
How does it handle large diffs?
It suggests using parallel subagents to review larger diffs for correctness, regressions, security, and intent fit.
Install review-and-ship
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
cursor/plugins