skills.rest
paulbrittain
paulbrittainCOMMUNITY
Explore all skills by this author →
GitHub

review-and-ship

Review feature branch diffs for bugs, regressions, and security issues.

Updated May 22, 2026
Search Tags:#testing#code review#pull request#continuous integration#commit hygiene#security checks
One-click install
npx skills add https://github.com/paulbrittain/claude-team-kit --skill review-and-ship-paulbrittain
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-and-ship
Source: https://github.com/paulbrittain/claude-team-kit/tree/main/skills/review-and-ship
Command: npx skills add https://github.com/paulbrittain/claude-team-kit --skill review-and-ship-paulbrittain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents broken, insecure, or mis-scoped changes from being shipped by ensuring the branch is thoroughly reviewed, adequately tested, and ready to merge.

Core Features & Use Cases

  • Targeted review for correctness and intent fit: Evaluates diffs for bugs, regressions, security concerns, and alignment with user intent.
  • Test-focused workflow with gap handling: Runs targeted tests for changed behavior and decides whether to add tests or document missing coverage.
  • Ship-ready PR management: Fixes critical issues, creates focused commits, pushes the branch, and opens or updates a PR with results captured in the output.

Quick Start

Use the review-and-ship skill to review your current branch against main, run targeted tests, fix critical issues, commit the focused changes, and open or update a PR.

Frequently Asked Questions about review-and-ship

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a feature branch for bugs and security issues before creating a pull request?▼

To review a feature branch for bugs and security issues, evaluate diffs for regressions and vulnerabilities while validating behavior with targeted tests. This workflow checks code changes for correctness, intent fit, and security concerns before safely committing and opening a pull request.

What is the best way to automate pre-merge testing and commit hygiene for continuous integration?▼

Automating pre-merge testing for continuous integration involves running targeted tests for changed behavior and deciding whether to add tests or document missing coverage. This enforces commit hygiene by fixing critical issues and creating focused commits before pushing the branch.

How do I prepare a pull request with test outcomes and a findings summary?▼

Preparing a pull request with test outcomes requires gathering diff context, running suggested checks, and rerunning affected tests after fixes. The workflow outputs a findings summary, test outcomes, and the PR URL, ensuring the branch is ready to merge.

Can I use a structured code review workflow to handle missing test coverage before merging?▼

A structured code review workflow handles missing test coverage by deciding whether to add tests or document the gaps. It runs targeted tests for changed behavior, fixes critical issues, and ensures the branch is thoroughly reviewed before merging.

Does continuous integration commit hygiene prevent broken or mis-scoped changes from being shipped?▼

Commit hygiene prevents broken or mis-scoped changes from being shipped by ensuring the branch is thoroughly reviewed, adequately tested, and ready to merge. It validates behavior with targeted tests and evaluates diffs for bugs, regressions, and security issues.

Related Skills

Explore More Software Engineering Skills→
DigicationDigication

commit

Generate conventional commit messages from changed files and diffs.

Official
Advanced
tunneleventunneleven

c4flow:merge

Merge pull requests into the main branch with pre-merge checks and post-merge cleanup.

Community
Intermediate
cxnaivecxnaive

requesting-code-review

Automate pre-commit code verification with static security analysis and regression checks.

Community
Advanced
himanshu231204himanshu231204
2

laravel-verification

Run a seven-phase Laravel verification pipeline covering environment, linting, tests, security, and migrations.

Community
Advanced