ship

Stages, commits, pushes, and opens a pull request on GitHub or GitLab in one guided flow.

Updated Jun 8, 2026

Search Tags:#git #code review #pull request #workflow automation #commit #github #gitlab

One-click install

npx skills add https://github.com/shawn-sandy/agentics-kit --skill ship-shawn-sandy

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/shawn-sandy/agentics-kit/tree/main/kit/plugins/git-agent/skills/ship
Command: npx skills add https://github.com/shawn-sandy/agentics-kit --skill ship-shawn-sandy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Shipping code requires a repetitive chain of git operations — staging, writing a conventional commit message, pushing, detecting the base branch, and drafting a PR body — each with its own failure modes like detached HEAD, unauthenticated CLIs, or missing worktree env files. This Skill runs the entire sequence as one guarded workflow that catches every blocker up front instead of failing mid-way. ## Core Features & Use Cases - Pre-flight guards: Runs five checks (clean tree, detached HEAD, default branch, CLI auth, worktree env parity) against the unmutated tree and reports all blockers in one table with verbatim remediation commands. - Conventional commits and PR creation: Generates a `<type>(<scope>): <description>` commit message from the staged diff, pushes with upstream tracking, detects existing PRs/MRs, and creates a structured PR body with Summary, Changes, Test Plan, and Linked Issues sections. - Adversarial self-review: Dispatches a fresh-context subagent to review the diff for no-op edits, vacuous tests, secrets, and regressions before pushing, amending confirmed fixes into the commit. - Use Case: After finishing a feature branch, ask to ship the changes — the Skill verifies the environment, commits with a formatted message, self-reviews the diff, pushes, and opens a GitHub PR or GitLab MR with linked issues auto-detected from completed plans. ## Quick Start Ask the assistant to ship my current changes and open a pull request for this branch.

Frequently Asked Questions about ship

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

FAQPage Schema

How do I commit and create a pull request in one step?▼

Invoke the ship flow on your feature branch: it stages all changes, writes a conventional commit message from the staged diff, pushes with upstream tracking, and creates a PR via gh or an MR via glab with a structured body.

Does this git workflow support GitLab as well as GitHub?▼

Yes, the platform is detected from the origin remote URL. GitHub remotes use the gh CLI and GitLab remotes use glab, with equivalent commands for auth checks, MR detection, and merge request creation.

What happens if a pre-commit hook fails during the commit?▼

The hook output is reported verbatim and the workflow stops immediately. It never retries, never uses --no-verify, and never modifies the staged files, leaving the fix to the user.

Can I skip the self-review step before pushing?▼

Yes, passing --no-review skips the self-review entirely. By default a fresh-context subagent reviews the diff against the base branch for defects, and confirmed findings are amended into the unpushed commit.

Why does shipping stop when I am on the main branch?▼

Shipping from the default branch is blocked by a pre-flight guard to prevent pushing directly to main or master. The report includes the remediation command git checkout -b <feature-branch> so you can switch first.