ship

Automates the release workflow of testing, reviewing, versioning, and creating pull requests.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/aicodepro/ai-agent-nexi --skill ship-aicodepro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/aicodepro/ai-agent-nexi/tree/main/agent/skills/gstack/ship
Command: npx skills add https://github.com/aicodepro/ai-agent-nexi --skill ship-aicodepro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping code involves a long, error-prone checklist: merging the base branch, running tests, auditing plan completion, reviewing the diff, bumping the version, updating the CHANGELOG, committing, pushing, and opening a PR. This Skill orchestrates that entire release pipeline so nothing is forgotten before code lands. ## Core Features & Use Cases - End-to-end release pipeline: Detects and merges the base branch, runs test suites, audits test coverage and plan completion, then bumps VERSION and regenerates the CHANGELOG from commit history. - Multi-layer review gates: Runs pre-landing checklist reviews, parallel specialist subagent reviews (security, performance, testing, maintainability), adversarial reviews via Claude and Codex, and Greptile comment triage before anything ships. - Automated PR creation: Syncs documentation, composes a structured PR body with redaction scanning, enforces version-prefixed titles, and creates or updates the PR/MR via gh or glab. - Use Case: After finishing a feature branch, tell the assistant to ship it — the Skill runs tests, reviews the diff with specialist subagents, fixes auto-fixable findings, writes the CHANGELOG entry, and opens a ready-to-merge PR. ## Quick Start Ask the assistant to ship the current branch and create a pull request for it.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I ship a feature branch and create a PR automatically?

Invoke the ship workflow on your feature branch. It merges the base branch, runs tests, reviews the diff with specialist subagents, bumps the version, updates the CHANGELOG, commits, pushes, and creates the PR via gh or glab.

What review checks run before code is shipped?

The workflow runs a pre-landing checklist review, parallel specialist subagent reviews covering security, performance, testing, and maintainability, plus adversarial reviews from Claude and Codex. Critical findings gate the ship until fixed or explicitly skipped.

Does the ship workflow support GitLab merge requests?

Yes, the workflow detects the hosting platform and uses glab to create or update merge requests on GitLab, with the same version-prefixed title and structured body format used for GitHub pull requests.

How is the CHANGELOG entry generated during a release?

The workflow enumerates every commit on the branch, reads the full diff, groups commits by theme, and writes a categorized entry with Added, Changed, Fixed, and Removed sections. Every commit must map to at least one bullet point.

What happens if plan items are incomplete when shipping?

A plan completion audit classifies each plan item as done, partial, not done, changed, or unverifiable. Missing items trigger a blocking gate where you choose to implement them, defer them as follow-up TODOs, or drop them from scope.

Why does the ship workflow stop after applying review fixes?

Any applied fix makes prior test results stale, so the workflow commits the fixes and stops, instructing you to re-run the ship command. This guarantees tests and reviews always run against the final code being pushed.