ship-cycle

Orchestrate GitHub release workflows into issues, milestones, and semver artifacts.

50|2|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/subinium/vibesubin --skill ship-cycle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship-cycle
Source: https://github.com/subinium/vibesubin/tree/main/plugins/vibesubin/skills/ship-cycle
Command: npx skills add https://github.com/subinium/vibesubin --skill ship-cycle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates end-to-end release planning and execution by turning improvement intent into a structured set of issues, milestones, and release artifacts, with durable audit trails across GitHub and local PRD tracks.

Core Features & Use Cases

  • Issue specification, milestone clustering, and deterministic release notes generation.
  • Dual-tracks operation (GitHub-hosted workflow and PRD local-trail) with idempotent mutation and preview-confirm-mutate safety checks.
  • Handoff to specialized skills (refactor-verify, setup-ci, write-for-ai, etc.) for each actionable item.

Quick Start

Run the ship-cycle skill to orchestrate a complete release from issue drafting to tagged release.

Frequently Asked Questions about ship-cycle

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

FAQPage Schema
How do I automate GitHub release cycles with structured milestones and issues?

Automate release cycles by turning improvement intent into a structured set of GitHub issues and semantic milestones mapped to semver versions. This enforces conventional commits and mandatory PR templates to generate deterministic release notes with a durable audit trail.

What is the best way to maintain an audit trail for local and GitHub-hosted release management?

Maintain a release management audit trail by operating on dual-tracks for GitHub-hosted workflows and PRD local-trails. This applies a reproducible mutation contract with preview-confirm-mutate safety checks and idempotent re-runs for safe, auditable deployments.

How do I generate deterministic release notes from conventional commits?

Generate deterministic release notes by clustering improvement intent into semantic milestones and enforcing conventional commits. This orchestrates an end-to-end workflow that produces structured release artifacts tied to a durable audit trail.

Can I use PRD local-tracks with GitHub milestones for end-to-end release planning?

Yes, you can use PRD local-tracks alongside GitHub milestones by operating dual-tracks. This requires multi-language frontmatter-driven context to orchestrate releases, applying a reproducible mutation contract for safe, idempotent local and remote deployments.

Does ship-cycle support idempotent re-runs for safe, auditable deployments?

Ship-cycle supports idempotent re-runs by applying a reproducible mutation contract with preview, confirm, and mutate phases. This ensures safe, auditable deployments across GitHub-hosted repos and PRD local-tracks without duplicating actions.

When do I need a reproducible mutation contract for release orchestration?

You need a reproducible mutation contract when orchestrating end-to-end release workflows that require strict auditability. It enforces a preview, confirm, and mutate sequence with idempotent re-runs, ensuring safe deployments across GitHub and local PRD tracks.