skills.rest
dungnt97
dungnt97COMMUNITY
Explore all skills by this author →
GitHub

ck:ship

Automate release shipping from feature branches to pull requests.

Updated Aug 27, 2026
Search Tags:#automation#git#release#pipeline#ship#pull-request
One-click install
npx skills add https://github.com/dungnt97/wallet-portal --skill ck-ship-dungnt97
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:ship
Source: https://github.com/dungnt97/wallet-portal/tree/main/claude/skills/ship
Command: npx skills add https://github.com/dungnt97/wallet-portal --skill ck-ship-dungnt97

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Ship pipelines: automate the end-to-end release workflow from a feature branch to a PR, including tests, reviews, version bumps, changelogs, journal entries, and docs updates before merging to main/master or dev/beta branches.

Core Features & Use Cases

  • End-to-end shipping: from feature/branch to a merged PR on the target branch.
  • Automated steps: pre-flight checks, tests, reviews, version bump, changelog generation, journal entry, and docs update.
  • Collaboration-ready: links issues, creates PRs, and enforces consistent commit messaging.

Quick Start

Invoke the ship command on a feature branch to trigger the full shipping pipeline and obtain the PR URL.

Frequently Asked Questions about ck:ship

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

FAQPage Schema
How do I automate git release shipping from a feature branch to a pull request?▼

You can automate release shipping by triggering a pipeline command on your feature branch, which runs pre-flight checks, tests, version bumps, changelog generation, and PR creation to merge into main/master or dev/beta branches.

What steps are included in an end-to-end feature branch release pipeline?▼

An end-to-end release pipeline includes pre-flight checks, automated tests, code reviews, version bumps, changelog generation, journal entries, docs updates, issue linking, automated merging, and safe push to create the final pull request.

Can I use automated shipping for multi-branch projects with dev and beta branches?▼

Yes, automated shipping pipelines are designed for multi-branch projects, supporting workflows that merge feature branches into main/master as well as dev/beta branches while maintaining consistent commit messaging and issue linking.

Does the release pipeline generate changelogs and update docs automatically?▼

Yes, the release pipeline automatically generates changelogs, creates background journal entries, and updates documentation as part of the end-to-end shipping process before the final pull request is created.

What's the best way to link issues and enforce consistent commit messages during git releases?▼

Using an automated shipping pipeline enforces consistent commit messaging and links issues automatically during the release process, ensuring collaboration-ready PRs without manual tracking or formatting errors.

Why do I need pre-flight checks before merging a feature branch to main?▼

Pre-flight checks are needed before merging to main to verify that tests pass, reviews are complete, and version bumps or changelog updates are applied, ensuring a safe push and preventing broken releases.

Related Skills

Explore More Software Engineering Skills→
Jason-Clark-FGJason-Clark-FG

playwright-validation

Validate UI changes on feature branches with Playwright end-to-end tests.

Community
Intermediate
dthuy62dthuy62

ck:ship

Merge a feature branch, run tests, and create a pull request.

Community
Advanced
dd-xiaozhidd-xiaozhi
2

release

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

Community
Advanced
yocxy2yocxy2

ship

Automate testing, adversarial review, changelog generation, and pull request creation.

Community
Advanced