ship

Commit code, create a pull request, and monitor CI status for merging.

Updated Mar 5, 2026

Search Tags:#automation #git #workflow #ci/cd #pull request #github

Ready to run

npx skills add https://github.com/matthiaskloft/claude-skills --skill ship-matthiaskloft

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/matthiaskloft/claude-skills/tree/main/workflow-automation/skills/ship
Command: npx skills add https://github.com/matthiaskloft/claude-skills --skill ship-matthiaskloft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the entire process of getting your completed code changes from your local machine into the main codebase, ensuring quality and smooth integration.

Core Features & Use Cases

Automated Commit & Push: Stages, commits, and pushes your code with a descriptive message.
Pull Request Creation: Generates a PR with a title, body, and fills out templates if available.
CI Monitoring & Auto-Merge: Delegates to the monitor-pr skill to track CI status and merge automatically upon success.
Post-Merge Cleanup: Ensures worktrees and branches are removed after a successful merge.
Use Case: After implementing a new feature phase, you can use this skill to automatically commit your work, open a pull request for review, and have it merged once all checks pass.

Quick Start

Use the ship skill to commit, create a PR, and merge the current changes.

Frequently Asked Questions about ship

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

FAQPage Schema

How do I automate git commit and pull request creation with CI monitoring?▼

Automating git commit and pull request creation with CI monitoring involves staging changes, pushing with a descriptive message, opening a PR, and tracking continuous integration status for merging. This workflow requires git and gh CLI to handle version control and PR operations.

What's the best way to auto-merge a GitHub pull request after CI checks pass?▼

The best way to auto-merge a GitHub pull request after CI checks pass is to delegate to a monitoring process that tracks continuous integration status and merges automatically upon success. Post-merge cleanup ensures worktrees and branches are safely removed.

Do I need gh CLI installed to automate GitHub pull request workflows?▼

Yes, you need gh CLI installed to automate GitHub pull request workflows. The automation requires both git and gh CLI for version control and pull request operations, including generating PR titles, filling out templates, and handling CI status monitoring.

How does state tracking work across sessions for CI/CD pull request automation?▼

State tracking for CI/CD pull request automation works by persisting workflow execution details across sessions, ensuring robust recovery and continuous monitoring. This guarantees that the commit, PR creation, and CI status monitoring pipeline resumes correctly without losing progress.

Does automated pull request creation fill out existing PR templates?▼

Yes, automated pull request creation fills out existing PR templates. When generating a pull request, the workflow creates a title and body, and automatically populates available templates to ensure documentation standards are met before opening the pull request.

What happens to local branches and worktrees after an automated pull request merge?▼

After an automated pull request merge, local branches and worktrees are automatically removed during post-merge cleanup. This ensures your environment stays clean and prevents obsolete worktrees or merged branches from accumulating.