ship

Automate commits, merges, and pull request creation for code delivery.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/adamway/thoughts-cli --skill ship-adamway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/adamway/thoughts-cli/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/adamway/thoughts-cli --skill ship-adamway

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies and automates the process of finalizing code work into reviewable, mergeable changes, ensuring consistency and safety before pushing to remote repositories.

Core Features & Use Cases

  • Automated Commit & Push: Captures all in-progress work, creates conventional commits, and pushes changes without manual intervention.
  • Pre-merge Validation: Ensures the working tree is clean, code review has been completed, and conflicts are resolved before deploying.
  • Use Case: When development is complete and a developer wants to automatically prepare a PR-ready branch with a full, clear history, they invoke this Skill to handle all steps from commit to PR creation seamlessly.

Quick Start

Use the ship skill to finalize your current feature branch by committing, merging with the main branch, and opening a pull request.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate finalizing and opening a pull request for my feature branch?

Automating pull request creation involves committing your code changes, merging with the main branch, and pushing to a remote repository. This skill handles those steps automatically, preparing a comprehensive PR description and ensuring a review-ready state.

What is the best way to ensure my code changes are review-ready before pushing?

To ensure code changes are review-ready before pushing, you need pre-merge validation that checks for a clean working tree, completed code reviews, and resolved conflicts. This skill automates those safety checks to align with team policies before deployment.

Can I automatically resolve merge conflicts when preparing my branch for a PR?

Automatically resolving merge conflicts during branch preparation requires validating the working tree and aligning changes with the main branch. This skill handles conflict resolution and verifies code review completion before pushing your finalized code.

How do I create conventional commits and push changes without manual intervention?

Creating conventional commits and pushing changes without manual intervention requires capturing in-progress work and formatting it automatically. This skill automates that process, building a clear commit history and pushing it directly to your remote repository.

Does this code finalization process work without additional CI/CD dependencies?

The code finalization process works without additional dependencies, operating autonomously to validate, merge, and push changes. It relies on your existing git setup to ensure a clean, review-ready state aligned with team policies.

When should I use an automated commit and merge workflow for my code changes?

You should use an automated commit and merge workflow when development is complete and you need to prepare a PR-ready branch. It streamlines code delivery by handling everything from conventional commits to pull request creation seamlessly.