ship

Automates merging, testing, versioning, and pull request creation for Git branches.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/TarunTeja44/portfolio --skill ship-tarunteja44
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/TarunTeja44/portfolio/tree/main/.agents/skills/gstack-ship
Command: npx skills add https://github.com/TarunTeja44/portfolio --skill ship-tarunteja44

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping code involves many repetitive, error-prone steps: merging the base branch, running tests, reviewing diffs, bumping versions, updating changelogs, committing, pushing, and opening a PR. This Skill automates that entire release workflow end-to-end so nothing gets forgotten. ## Core Features & Use Cases - Automated Ship Pipeline: Detects the base branch, merges it into your feature branch, runs test suites, reviews the diff, bumps VERSION, updates CHANGELOG, commits, pushes, and creates a PR via GitHub CLI. - Review Readiness Gate: Displays a dashboard of engineering, CEO, design, and adversarial review statuses, blocking shipping when required reviews are missing or stale. - Test Framework Bootstrap: Detects your runtime (Node, Ruby, Python, Go, Rust, PHP, Elixir) and sets up a test framework, CI workflow, and TESTING.md if none exists. - Use Case: You finished a feature branch and say "ship it" — the Skill merges main, runs tests, triages failures, generates the changelog, and outputs the PR URL without further prompts. ## Quick Start Ask the assistant to ship the current feature branch by running the ship workflow and creating a pull request.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate creating a pull request from a feature branch?

Run the ship workflow, which detects the base branch, merges it into your feature branch, runs tests, bumps the version, updates the changelog, commits, pushes, and creates the PR using the GitHub CLI. It outputs the PR URL when finished.

What happens when tests fail during the ship workflow?

Failing tests are triaged by ownership: failures caused by files changed on your branch block the ship, while pre-existing failures from the base branch are flagged but do not automatically stop the workflow. Merge conflicts that cannot be auto-resolved also stop the run.

Does the ship workflow require a code review before merging?

Yes, an engineering review is required by default and shown in the Review Readiness Dashboard. You can override the gate interactively, or disable it globally with the skip_eng_review config setting. CEO, design, and adversarial reviews are informational and never block.

Can the ship workflow set up tests if my project has none?

Yes, it detects your runtime from files like package.json or Gemfile, recommends a test framework such as vitest or pytest, installs it, writes example tests, creates a GitHub Actions CI workflow, and documents everything in TESTING.md.

When should I not use the automated ship workflow?

Avoid it when you are on the base branch itself, when merge conflicts require human judgment, or when a MINOR or MAJOR version bump is needed since those require an explicit decision. It is designed for routine feature-branch releases.