review-and-ship

Review diffs against the base branch, assess risk, and run tests before shipping.

3|1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/cogine-ai/cogine-dev-skillset --skill review-and-ship-cogine-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-and-ship
Source: https://github.com/cogine-ai/cogine-dev-skillset/tree/main/skills/review-and-ship
Command: npx skills add https://github.com/cogine-ai/cogine-dev-skillset --skill review-and-ship-cogine-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review and ship changes by performing structured code reviews, closing key issues, and updating or opening PRs to reflect changes.

Core Features & Use Cases

  • Structured review workflow: compare diffs against the base, assess risk, and verify tests before merging.
  • Issue closure and PR hygiene: automatically close issues when appropriate and update PR descriptions and metadata.
  • Traceable shipping: push changes via PR and generate an auditable record of decisions for future reference.

Quick Start

Review a diff, run tests, and push a branch to open or update the 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 git diff and ensure tests pass before shipping?

A structured code review compares diffs against the base branch, assesses risk, and verifies tests pass before opening a pull request. This ensures changes are safe to ship and generates an auditable record of decisions.

Can I automatically close issues and update pull request descriptions?

Yes, you can automatically close key issues when appropriate and update PR descriptions and metadata. This maintains PR hygiene and generates an auditable record of decisions for future reference.

Does this code review workflow support Git-based projects with CI checks?

Yes, it applies to typical software projects with Git-based workflows, multiple environments, and CI checks. It ensures review and PR processes govern releases by verifying tests and assessing risk before merging.

What's the best way to create an auditable record of code review decisions?

Push changes via a PR after verifying tests to produce a findings summary, test outcomes, and the PR URL. This documents decisions and enables traceability for the shipping process.

How do I assess risk in a pull request before merging?

Identify diffs against the base branch and evaluate their potential impact before changes pass tests. This produces a findings summary to guide safe shipping decisions.