dharma-ship

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

1|3|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/AIKAGRYA/dharma_swarm --skill dharma-ship-aikagrya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dharma-ship
Source: https://github.com/AIKAGRYA/dharma_swarm/tree/main/mode_pack/claude/ship
Command: npx skills add https://github.com/AIKAGRYA/dharma_swarm --skill dharma-ship-aikagrya

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 Readiness Gate: Syncs with main and runs the test suite, stopping immediately on failures or unresolved critical blockers. - Version and Changelog Discipline: Applies version updates and produces release notes as required outputs. - PR and Release Automation: Pushes the branch and 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 Ship my current ready branch by syncing with main, running tests, updating the version and changelog, and opening the pull request.

Frequently Asked Questions about dharma-ship

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

FAQPage Schema
How do I ship a ready branch with tests and a pull request?▼

Invoke this release mode on a finished branch. It syncs with main, runs the test suite, applies version and changelog updates, then pushes and opens the PR or release artifact automatically.

What happens if tests fail during the release process?▼

The workflow stops immediately on failed tests or unresolved critical blockers. It does not push, version, or open a PR until the branch passes cleanly.

When should I not use this release mode?▼

Do not use it to decide what to build or on branches that are not ready to land. It is strictly for branches that have completed development and review and only need the release steps executed.

What outputs does the release workflow produce?▼

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