skills.rest
NUMU-IO
NUMU-IOOFFICIAL
Explore all skills by this author →
WebsiteGitHub

speckit-ship-run

Automates release shipping workflows and pull request preparation for spec-driven feature branches.

2|Updated Jan 6, 2026
Search Tags:#changelog#git workflow#pull requests#release automation#branch sync#ci verification
One-click install
npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-ship-run-numu-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-ship-run
Source: https://github.com/NUMU-IO/NUMU-api/tree/main/.agents/skills/speckit-ship-run
Command: npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-ship-run-numu-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual overhead of shipping a completed feature by coordinating readiness checks, branch synchronization, changelog updates, CI validation, and pull request creation.

Core Features & Use Cases

  • Release Readiness Checks: Verifies task completion, review status, QA results, and working tree cleanliness before any shipping action.
  • Branch and CI Orchestration: Synchronizes feature branches with the target branch, checks build status, and helps prevent shipping from a broken state.
  • PR and Artifact Generation: Creates structured pull request descriptions, updates changelogs, and archives release artifacts for traceability.
  • Use Case: A developer has finished a feature and needs a safe, auditable path from implementation to a reviewable pull request with release notes.

Quick Start

Ask the skill to ship the current feature branch and prepare the release pull request with readiness checks, changelog updates, and CI verification.

Frequently Asked Questions about speckit-ship-run

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

FAQPage Schema
How do I automate release readiness checks before creating a pull request?▼

Automating release readiness checks verifies task completion, review status, QA results, and working tree cleanliness before initiating any pull request creation or branch synchronization actions.

How do I generate a changelog and prepare a release pull request from a feature branch?▼

Generating a changelog and preparing a release pull request involves applying spec-kit artifacts and git history to create structured PR descriptions, update release notes, and archive artifacts for traceability.

Do I need the GitHub CLI to synchronize feature branches and verify CI status?▼

You need optional GitHub CLI access to fully execute branch synchronization, CI verification, and PR creation, alongside required spec-kit artifacts and local git history for guarded confirmation.

What is the safest way to rebase a feature branch before shipping a release?▼

The safest way to rebase a feature branch before shipping uses guarded confirmation steps to validate CI build status and synchronize with the target branch, preventing pushes from a broken state.

Can I prevent shipping a release when my working tree has uncommitted changes?▼

You can prevent shipping a release with uncommitted changes because release readiness checks explicitly validate working tree cleanliness and CI build status before allowing any branch synchronization.

Related Skills

Explore More Software Engineering Skills→
juvenaljuvenal
8

speckit-git-validate

Validate Git feature branch names against sequential or timestamp patterns.

Community
Intermediate
toqoztoqoz

github-release-pr

Automate GitHub release pull requests between development and production branches.

Community
Advanced
johan-Rmjohan-Rm

create-pr

Automate commit linting, quality gates, and Pull Request creation via GitHub CLI.

Community
Advanced
lemiglemig

ship

Orchestrate software shipping from base-branch detection to PR creation.

Community
Intermediate