ship

Automate Git workflows from linting to pull request creation.

Updated Feb 27, 2026

Search Tags:#git #pull request #workflow automation #commit #CI

Ready to run

npx skills add https://github.com/wutongshenqiu/prism --skill ship-wutongshenqiu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/wutongshenqiu/prism/tree/main/.agents/skills/ship
Command: npx skills add https://github.com/wutongshenqiu/prism --skill ship-wutongshenqiu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the Git workflow, automating steps like linting, testing, committing, pushing, creating pull requests, and waiting for CI, making the process more efficient and less error-prone.

Core Features & Use Cases

End-to-End Workflow: Automates the entire commit process, from linting and testing to creating pull requests and waiting for CI.
PR Creation: Detects existing pull requests and creates new ones as needed.
Merge Support: Supports auto-merging pull requests after CI passes.
Use Case: Ideal for developers looking to reduce manual steps in their Git workflow, improving productivity and reducing the risk of errors.

Quick Start

Run the ship command with your commit message.

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 workflow from commit to pull request merge?▼

You can automate your Git workflow end-to-end by running a command that handles linting, testing, committing, pushing, creating pull requests, and waiting for CI. This reduces manual steps and supports auto-merging after CI passes.

What is the best way to automate pull request creation and CI waiting?▼

The best way to automate pull request creation and CI waiting is using a workflow tool that detects existing PRs, creates new ones as needed, and pauses execution until CI checks pass. This ensures safe, automated branch management and merging.

Do I need GitHub CLI to automate Git commit and push workflows?▼

Yes, you need Git and GitHub CLI to automate Git commit and push workflows. The GitHub CLI is required to detect existing pull requests, create new ones, and manage auto-merging after CI checks pass.

Can I auto-merge a pull request after CI passes automatically?▼

Yes, you can auto-merge a pull request after CI passes automatically. The workflow automation handles branch management and pull request creation, waiting for CI validation to complete successfully before merging.

Does automated Git workflow handle linting and testing before committing?▼

Yes, automated Git workflow handles linting and testing before committing. The end-to-end process runs linting and testing as initial steps, ensuring code quality checks pass before committing and pushing changes to your repository.

Why does my automated pull request workflow fail to detect existing branches?▼

Automated pull request workflows fail to detect existing branches if Git or GitHub CLI are not properly authenticated or configured. Ensure both are installed and authenticated to allow proper branch management and PR detection.