ship

Orchestrate end-to-end release workflows from tests to PR creation.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/ignidus/iscagent --skill ship-ignidus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/ignidus/iscagent/tree/main/skills/ship
Command: npx skills add https://github.com/ignidus/iscagent --skill ship-ignidus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fully automated release workflow. Handles: testing, code review, versioning, changelog generation, commit organization, and PR creation with minimal user intervention.

Core Features & Use Cases

  • Automates testing, review, version decisions, changelog entry, and PR creation for releases.
  • Enforces clean, bisectable commits and an evidence trail for every release.
  • Works across feature branches and infrastructure changes to produce auditable release candidates.

Quick Start

Install the ship skill on your project and trigger a release by naming the changes you want shipped.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate a release pipeline from testing to PR creation?

Automating a release pipeline from testing to PR creation involves orchestrating pre-flight checks, test execution, versioning decisions, changelog generation, and standardized commit history. This workflow produces auditable release candidates with minimal user intervention.

What is the best way to enforce clean and bisectable commits for versioning?

Enforcing clean, bisectable commits for versioning is achieved by automatically organizing commit history and applying standardized commit formats. This creates an evidence trail for every release candidate generated across feature and infrastructure changes.

Can I automate changelog generation and versioning decisions for infrastructure changes?

Automating changelog generation and versioning decisions for infrastructure changes is fully supported. The workflow applies the same automated testing, review, and PR creation processes used for feature branches to infrastructure modifications.

How do I generate an auditable release candidate with an evidence trail?

Generating an auditable release candidate with an evidence trail requires running automated pre-flight checks, executing tests, and enforcing standardized commit history. The workflow organizes commits and generates changelog entries to satisfy review requirements.

Does automated release workflow require manual code review before PR creation?

Automated release workflow includes automated review steps before PR creation, while standardized commit history and changelog generation provide the evidence trail for human review. The process orchestrates these checks to produce ready-to-review release candidates.