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.
Install
npx skills add https://github.com/cursor/plugins --skill review-and-shipSKILL.md
Review and ship
Trigger
Reviewing changes before shipping. Close key issues, verify behavior, and open or update a PR.
Workflow
- Gather context: diff against base branch, uncommitted changes, recent commits, changed files, and user intent from recent relevant chats if useful.
- Run targeted tests for changed behavior. If no focused tests exist, decide whether to add them or document the gap.
- Review for correctness, regressions, security, and intent fit. Use parallel subagents for larger diffs.
- Fix critical issues before finalizing and re-run affected tests.
- Commit selective files with a concise message.
- 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,link
Guardrails
- 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-architecturemattpocock1MScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.codebase-designmattpocock691KShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.web-design-guidelinesvercel-labs676KReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".code-reviewmattpocock631KReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".