ship

Automate release workflows to verify, build, test, deploy, and announce software releases.

2|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Wilder1222/superomni --skill ship-wilder1222
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/Wilder1222/superomni/tree/main/skills/ship
Command: npx skills add https://github.com/Wilder1222/superomni --skill ship-wilder1222

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual release processes are error-prone and hard to audit; this skill automates a repeatable release workflow from verification to announcement.

Core Features & Use Cases

  • End-to-end release orchestration across CI/CD: verify, build, test, deploy, and publish.
  • Versioning and changelog automation with deterministic tagging and release notes.
  • Auditable artifacts and gates to ensure compliant, production-ready releases.

Quick Start

Install and run the ship skill to automate your next release with a single activation.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate a complete CI/CD release workflow from verification to deployment?▼

You can automate a complete CI/CD release workflow by orchestrating verify, build, test, deploy, and publish steps in a single process. This ensures consistent, auditable software releases with built-in safeguards and traceable artifacts.

How does automated versioning and changelog generation work for production launches?▼

Automated versioning and changelog generation works by applying deterministic tagging and generating release notes during the workflow. This enforces versioning updates and changelog automation for compliant, production-ready releases.

Can I enforce pre-release checks and deployment verifications across my CI/CD pipelines?▼

Yes, you can enforce pre-release checks and deployment verifications across CI/CD pipelines. The workflow applies auditable artifacts and gates to ensure consistent, compliant production launches and public deployments.

What is the best way to prevent manual deployment errors during feature releases?▼

The best way to prevent manual deployment errors during feature releases is to automate a repeatable release workflow. Replacing manual processes with automated orchestration ensures traceable artifacts and eliminates error-prone steps.

Do I need any specific dependencies to run an end-to-end release workflow with verification?▼

No specific dependencies are required to run an end-to-end release workflow with verification. You can apply this workflow to production launches and public deployments across existing CI/CD pipelines without additional component installations.