Review And Ship
- 1.4k installs
- 2.5k repo stars
- Updated August 5, 2026
- cursor/plugins
review-and-ship is a Cursor skill that reviews branch diffs for bugs and intent fit, runs or writes tests, commits focused work, and opens PRs for developers preparing to deploy.
About
review-and-ship is a Cursor plugin skill for systematic pre-deploy review on the current branch. The workflow gathers diff context against the base branch, uncommitted changes, recent commits, and user intent, then runs targeted tests for changed behavior or documents coverage gaps. It reviews for correctness, regressions, security, and intent fit—using parallel subagents on larger diffs—fixes critical issues, commits focused work, and opens or updates a pull request. Developers reach for review-and-ship when a feature branch is ready for human review and merge rather than ad-hoc diff skimming without test verification.
- Automated multi-pass code review focused on correctness, security, and maintainability
- Generates a ship decision with clear severity buckets and remediation steps
- Hard-gate workflow that only approves production-ready changes
- Includes next-skill handoff to automated testing or deployment
- 409 installs across Cursor users
Review And Ship by the numbers
- 1,394 all-time installs (skills.sh)
- +210 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #90 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/cursor/plugins --skill review-and-shipAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.4k |
|---|---|
| repo stars | ★ 2.5k |
| Last updated | August 5, 2026 |
| Repository | cursor/plugins ↗ |
How do you review a branch before opening a PR?
Get systematic, high-signal code review and launch-readiness checks before every deploy.
Who is it for?
Cursor users with a feature branch ready for systematic review, test verification, and PR creation before merge.
Skip if: Greenfield prototyping with no branch diff or teams that only need lint fixes without test runs or PR workflow.
When should I use this skill?
The user is reviewing changes before shipping, needs test verification, or wants to open or update a PR on the current branch.
What you get
Reviewed diffs, executed or added tests, focused commits, and an opened or updated pull request.
- Pull request
- Test execution results
- Focused commits
Files
Review and ship
Trigger
Reviewing changes before shipping. Close key issues, verify behavior, and open or update a PR.
Workflow
1. Gather context: diff against base branch, uncommitted changes, recent commits, changed files, and user intent from recent relevant chats if useful. 2. Run targeted tests for changed behavior. If no focused tests exist, decide whether to add them or document the gap. 3. Review for correctness, regressions, security, and intent fit. Use parallel subagents for larger diffs. 4. Fix critical issues before finalizing and re-run affected tests. 5. Commit selective files with a concise message. 6. Push branch and open or update a PR.
Suggested Checks
git fetch origin main
git diff origin/main...HEAD
git status
gh pr checks --json name,bucket,state,workflow,linkGuardrails
- Prioritize correctness, security, and regressions over style-only comments.
- Keep commits focused and avoid unrelated file changes.
- If pre-commit checks fail, fix the issues rather than bypassing hooks.
- Use
gh pr checksinstead of GitHub Actions-only commands when judging PR readiness.
Output
- Findings summary (critical, warning, note)
- Tests run and outcomes
- PR URL
Related skills
Improve Codebase ArchitectureSafely deepen clusters of shallow modules into cohesive, testable units while respecting their external dependencies.566k196k
Caveman ReviewGet ultra-compressed, one-line code review comments that cut noise while keeping every actionable fix.270k94.7kCodebase DesignShared vocabulary for designing deep modules: improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable.266k196kCavecrewDelegate coding tasks to specialized subagents that return compressed output, keeping the main context window usable for much longer sessions.220k94.7kCode ReviewReviews a branch or PR diff on two axes at once: conformance to coding standards plus a code-smell baseline, and whether it actually implements the original spec.201k196k
Requesting Code ReviewDispatch a consistent, high-signal code reviewer subagent that catches plan deviations and quality issues before merging or continuing development.183k264kHow it compares
Use review-and-ship over bare diff review when test execution, security checks, and PR creation should happen in one workflow.
FAQ
What does review-and-ship check before merge?
review-and-ship gathers branch diffs, runs targeted tests for changed behavior, and reviews for correctness, regressions, security, and intent fit. Critical fixes are committed before opening or updating a pull request.
Does review-and-ship write tests?
review-and-ship runs existing targeted tests first. When no focused tests exist for changed behavior, the skill decides whether to add them or document the coverage gap before shipping.