skills.rest
pillip
pillipCOMMUNITY
Explore all skills by this author →
GitHub

ship

Run tests, update docs and changelog, and merge PRs when deployment-ready.

11|Updated Feb 18, 2026
Search Tags:#workflow#changelog#deployment#merge#docs#ci#tests
One-click install
npx skills add https://github.com/pillip/claude-dev-kit --skill ship-pillip
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/pillip/claude-dev-kit/tree/main/skills/ship
Command: npx skills add https://github.com/pillip/claude-dev-kit --skill ship-pillip

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Finalizes tests, docs, and changelog for a PR and merges it when the code is deployment-ready, eliminating manual handoffs and drift.

Core Features & Use Cases

  • Automated finalization: runs tests, updates documentation and changelog, and merges PRs when criteria are met.
  • Sprint-aware merging: respects issues.md tracking and sprint state to avoid premature merges.
  • Guarded workflow: enforces checkpoint validation and registry updates to main for safe handoffs.

Quick Start

Run the ship workflow on the current branch to finalize and merge the PR.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate PR finalization for tests, docs, and changelog updates before merging?▼

Automated PR finalization runs tests, updates documentation and the changelog, and merges the branch when deployment readiness is achieved. It eliminates manual handoffs by coordinating checkpoint validation and registry updates to main for safe merges.

What is the best way to merge pull requests safely in sprint-enabled projects?▼

Sprint-aware merging respects issues.md tracking and sprint state to avoid premature merges. It enforces PR review gates and executes automated ship steps, ensuring code is deployment-ready before merging to main.

Do I need authenticated GitHub access to automate deployment readiness checks and PR merges?▼

Authenticated GitHub access is required to automate deployment readiness checks and PR merges. The workflow coordinates issues.md state, PR review gates, and registry updates to main, needing authenticated permissions to enforce checks and execute safe merges.

How does checkpoint validation prevent premature merges during CI workflow automation?▼

Checkpoint validation prevents premature merges by enforcing PR review gates and registry updates to main. The workflow coordinates issues.md state and automated ship-step execution, ensuring all tests, docs, and changelog updates pass before merging.

Can I use automated changelog updates and docs finalization without sprint tracking?▼

Automated changelog updates and docs finalization apply specifically to PRs inside sprint-enabled projects. The workflow relies on issues.md state tracking and sprint state to coordinate safe merges, so non-sprint projects are not supported.

Why does my automated PR merge fail when deployment readiness checks are not met?▼

Automated PR merges fail when deployment readiness checks are not met because the workflow enforces checkpoint validation and PR review gates. It requires successful test execution, documentation updates, and registry updates to main before merging.

Related Skills

Explore More Software Engineering Skills→
limzivectorlimzivector

document-release

Automate post-ship documentation updates to reflect codebase changes.

Community
Advanced
dd-xiaozhidd-xiaozhi
2

release

Automate software releases with CI/CD triggers, pre-deployment validation, and post-release governance.

Community
Advanced
jkomorosjkomoros
9

git-workflow

Automate Git rebases, conflict resolution, and pull request creation with gh pr.

Community
Intermediate
HomericIntelligenceHomericIntelligence
18

verify-pr-ready

Validate GitHub Pull Requests for CI status, approvals, and merge conflicts.

Official
Intermediate