mcpField
R
review-and-ship

review-and-ship

github.com/cursorTesting & quality14.5k2.5k installsUpdated today
Repository

About review-and-ship

Review and ship is a skill for reviewing code changes before release, addressing key issues, validating behavior, and opening or updating a pull request. Its workflow combines targeted testing, risk-focused review, selective commits, and PR readiness checks.

Key features

  1. 01Gather diffs, commits, and change context
  2. 02Run targeted tests and assess coverage gaps
  3. 03Review correctness, security, and regressions
  4. 04Fix critical issues and rerun affected tests
  5. 05Commit selected files and update a PR

Use cases

  1. 01Prepare a branch for release
  2. 02Validate behavior after code changes
  3. 03Review a larger diff with parallel subagents
  4. 04Check pull request readiness

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/cursor/plugins --skill review-and-ship

After installing, type/review-and-shipin Claude Code to confirm it loaded.

Details

From the project README

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,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 checks instead of GitHub Actions-only commands when judging PR readiness.

Output

  • Findings summary (critical, warning, note)
  • Tests run and outcomes
  • PR URL

Comments

Markdown supported