ship

Automate the pull request lifecycle from commit to merge.

1|1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/gamaware/system-design-course --skill ship-gamaware
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/gamaware/system-design-course/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/gamaware/system-design-course --skill ship-gamaware

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the entire process of getting code changes from your local machine into the main branch, handling documentation, commits, pull requests, CI checks, and code reviews.

Core Features & Use Cases

  • Automated Workflow: Manages the end-to-end lifecycle of a pull request, from initial commit to final merge.
  • Integrated Reviews: Monitors and helps address feedback from AI code reviewers like CodeRabbit and Copilot.
  • CI/CD Assurance: Ensures all automated checks pass before merging.
  • Use Case: After completing a new feature, you can tell the AI "ship it" and it will automatically update documentation, create a PR, wait for CI to pass, help you address any review comments, and then merge the code.

Quick Start

Use the ship skill to finalize and land your changes, passing the PR number if you are resuming monitoring an existing PR.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate the GitHub pull request lifecycle from commit to merge?

Automating the GitHub pull request lifecycle is handled by orchestrating documentation updates, conventional commits, PR creation, CI/CD monitoring, and code review management into a single workflow. This ensures all checks pass and reviews are addressed before merging code.

Can I use AI to help address code review comments on a pull request?

AI can monitor and help address feedback from AI code reviewers like CodeRabbit and Copilot. It tracks review comments on your pull request and assists in resolving the requested changes before the final merge.

How do I monitor an existing pull request after restarting my developer workflow?

To monitor an existing pull request, you can pass the PR number as an argument to resume tracking. The system will pick up where it left off, waiting for CI/CD checks to pass and helping address any outstanding code reviews.

What's the best way to ensure CI/CD checks pass before merging a pull request?

Ensuring CI/CD checks pass before merging is achieved by automating the monitoring of your pull request status. The workflow waits for all automated checks to complete successfully and only proceeds to merge the code after receiving a green status.

Does this automated PR workflow support conventional commits and documentation updates?

Yes, the automated PR workflow supports conventional commits and documentation updates. When you finalize changes, it automatically handles commit formatting and updates relevant documentation before creating the pull request.

When should I not use an end-to-end pull request automation workflow?

You should avoid end-to-end pull request automation workflows for trivial changes requiring manual commit manipulation or complex merge conflicts needing interactive human resolution. The automation is designed for standard developer workflows where checks and reviews can be systematically verified.