ship

Automate Git release workflows from code completion to pull request readiness.

1|1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/putrawitama/DenchClaw --skill ship-putrawitama
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/putrawitama/DenchClaw/tree/main/skills/gstack/ship
Command: npx skills add https://github.com/putrawitama/DenchClaw --skill ship-putrawitama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end release workflow from code complete to PR readiness, eliminating manual handoffs and reducing cycle time.

Core Features & Use Cases

  • Sync with the base branch and merge changes from the feature branch.
  • Run project-appropriate tests and ensure all tests pass across ecosystems.
  • Audit test coverage for changed files and prepare a PR-ready branch.
  • Push the updated branch to the remote and open a pull request via GitHub.
  • Bootstraps test frameworks if needed and sets up environment quickly.

Quick Start

Kick off the Ship workflow to take your branch from code complete to PR ready for review.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate my Git release workflow from code complete to PR ready?

You can automate the Git release workflow by using a tool that syncs your feature branch with the base branch, runs multi-language tests, audits coverage, and opens a pull request via the GitHub CLI. This eliminates manual handoffs from code complete to PR readiness.

Can I sync my feature branch with the base branch and run tests automatically?

Yes, you can sync your feature branch with the base branch and automatically run project-appropriate tests. The workflow merges changes, executes the test suite across multiple ecosystems, and ensures all tests pass before proceeding.

Does this automation tool bootstrap test frameworks if my project lacks them?

Yes, the automation tool bootstraps test frameworks if needed and sets up the environment quickly. It detects the project ecosystem, applies the appropriate tests, and performs a coverage audit on changed files before pushing the branch.

How do I open a pull request via the GitHub CLI after passing tests?

To open a pull request via the GitHub CLI after passing tests, the workflow pushes your updated branch to the remote repository and then creates the PR automatically. This ensures the PR-ready branch contains synced, tested, and audited code.

What is the best way to audit test coverage for changed files before creating a PR?

The best way to audit test coverage for changed files is to use an automated workflow that performs a coverage audit after syncing and test execution. This prepares a PR-ready branch by ensuring all changed files meet coverage requirements before pushing.