skills.rest
AmitabhainArunachala
AmitabhainArunachalaCOMMUNITY
Explore all skills by this author →
GitHub

dharma-ship

Automates branch release with tests, versioning, changelog, and PR creation.

Updated Aug 5, 2026
Search Tags:#git#testing#changelog#versioning#pull request#release#ci
One-click install
npx skills add https://github.com/AmitabhainArunachala/dharma_swarmv.01 --skill dharma-ship-amitabhainarunachala
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dharma-ship
Source: https://github.com/AmitabhainArunachala/dharma_swarmv.01/tree/main/mode_pack/claude/ship
Command: npx skills add https://github.com/AmitabhainArunachala/dharma_swarmv.01 --skill dharma-ship-amitabhainarunachala

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping a finished branch involves repetitive, error-prone steps: syncing with main, running tests, bumping versions, updating changelogs, and opening pull requests. This Skill enforces a disciplined release workflow so nothing is skipped before code lands. ## Core Features & Use Cases - Release Checklist Enforcement: Syncs with main, runs the test suite, and stops on failures or unresolved critical blockers. - Version and Changelog Discipline: Applies version updates and produces release notes as required outputs. - PR and Handoff Automation: Pushes the branch, opens the PR or release artifact, then hands off to QA verification and retrospective modes. - Use Case: A developer finishes a feature branch and invokes this mode to run tests, bump the version, write release notes, and open the pull request in one guided pass. ## Quick Start Use the dharma-ship mode to run tests, update the version and changelog, and open a pull request for my ready branch.

Frequently Asked Questions about dharma-ship

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

FAQPage Schema
How do I automate a release workflow with tests and versioning?▼

Use a release mode that syncs your branch with main, runs the full test suite, applies version and changelog updates, then pushes and opens the pull request. This Skill enforces exactly that sequence and stops on any test failure.

When should I use a ship or release mode for a branch?▼

Use it only when the branch is already ready to land, meaning implementation and review decisions are done. It is not for deciding what to build; it handles tests, versioning, changelog, and PR creation for finished work.

What happens if tests fail during the release process?▼

The workflow stops immediately on failed tests or unresolved critical blockers. No version bump, push, or pull request occurs until the failures are fixed and the branch is genuinely ready.

What outputs does a disciplined release workflow produce?▼

It produces four required outputs: test results, release notes, a version update, and the PR or release status. After shipping, handoff goes to QA for release verification and a retrospective after completion.

Can release automation run without manual interaction?▼

Yes, once the branch is truly ready the workflow prefers non-interactive automation. Syncing, testing, versioning, and PR creation proceed automatically, halting only on test failures or critical blockers.

Related Skills

Explore More Software Engineering Skills→
xhyqaqxhyqaq
63

acceptance-testing

Verify completed feature branches against predefined acceptance criteria before merging.

Community
Advanced
jmolzjmolz

source-command-self-heal

Capture lessons learned and generate rules from completed work.

Community
Advanced
adryanmoldokkr32-pixeladryanmoldokkr32-pixel

land-and-deploy

Merge pull requests, monitor CI, deploy to production, and verify health with canary checks.

Community
Intermediate
hetsheth-droidhetsheth-droid

land-and-deploy

Merge PRs, wait for CI, deploy to production, and verify canary health.

Community
Advanced