A workflow that pushes the current code branch to GitHub and opens a pull request, which is a request for others to review and merge changes.

It helps verify GitHub CLI access, authentication, and remotes, then create a branch, push changes, and open a pull request.

It handles the preparation and checks needed to send local work to GitHub for review.

spec-ship — Skill for Claude Code by benjaminthomas/spec-driven-dev

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add benjaminthomas/spec-driven-dev --skill spec-ship

Clone the repo

git clone --depth 1 https://github.com/benjaminthomas/spec-driven-dev

Made for: Claude Code.

Or install spec-driven-dev, the plugin that ships this one along with the rest of its 6 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/benjaminthomas/spec-driven-dev/spec-ship/github.svg)](https://agentmods.dev/skills/benjaminthomas/spec-driven-dev/spec-ship)

Your own site

<a href="https://agentmods.dev/skills/benjaminthomas/spec-driven-dev/spec-ship"><img src="https://agentmods.dev/badge/skills/benjaminthomas/spec-driven-dev/spec-ship/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/benjaminthomas/spec-driven-dev/spec-ship"><img src="https://agentmods.dev/badge/skills/benjaminthomas/spec-driven-dev/spec-ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 119 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,649 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00119	$0.01649
Opus 5.5	$0.00048	$0.00660
Sonnet 5.5	$0.00024	$0.00330
Haiku 4.5	$0.00012	$0.00165

Measured 1mo ago against content hash 594016f91e3d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

spec-ship scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/spec-ship/SKILL.md · 202 lines

How it starts

The opening of the file, as written. The whole thing — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Ship It

Push your work to GitHub and open a pull request — handling prerequisites, branch creation, pushing, and PR generation automatically.

This skill complements spec-checkpoint. Use spec-checkpoint to commit locally (with quality gates), then spec-ship to get the code to GitHub for review.

Instructions

Step 0: Prerequisites

Verify tooling before doing anything else.

GitHub CLI installed?
```
gh --version
```
If the command fails (not found):
- Detect the platform and attempt to install:
  - Windows: winget install --id GitHub.cli
  - macOS: brew install gh
  - Linux (Debian/Ubuntu): follow the official apt instructions
- If auto-install fails, tell the user what to install and stop.

GitHub CLI authenticated?

gh auth status

If not authenticated, tell the user:

GitHub CLI is not logged in. Please run this in the prompt:
  ! gh auth login
Then re-run /spec-ship.

Stop here — do not proceed until auth is confirmed.

Git remote exists?

git remote -v

If no remote named origin exists, stop and tell the user:

No git remote found. Add one with:
  git remote add origin https://github.com/{user}/{repo}.git

Step 1: Detect the Environment

Run these commands to understand the current state:

git branch --show-current — get the current branch name

Detect the default branch:

gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'

git status --porcelain — check for uncommitted changes

If there are uncommitted changes, stop and tell the user:

You have uncommitted changes. Run /spec-checkpoint first to commit them, then /spec-ship to push.

Store the default branch name for use throughout the remaining steps.

Step 2: Check for Unpushed Commits

Determine if there are commits that haven't been pushed yet.

If on a feature branch with a remote tracking branch:

git log @{upstream}..HEAD --oneline

Read the full file on GitHub · 202 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 202 lines · 119 tokens per session scan A 594016f91e3d

Subscribe to this mod's changes

spec-ship is a skill published in the GitHub repository benjaminthomas/spec-driven-dev (1 stars, last pushed 2mo ago), licensed MIT. It adds 119 tokens to every session and 1,649 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code Git and workflow agent-skills ai-agents antigravity codex-cli cursor

git-workflow-and-versioning

Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…

addyosmani/agent-skills · 89 tokens

repo-activity-summary

Summarize a repository's recent engineering activity from git history — technologies, work types, churn hotspots, contributor patterns, and velocity. Use when asking "what has this repo been working on", "is this project active", "who contributes what", "where are the hotspots", or before onboarding onto an unfamiliar…

CodeAlive-AI/ai-driven-development · 70 tokens

polya-fast-track

Bypass Mode of the Pólya Heuristic Coder: Routine One-Shot Surgical Fixes, Minor Refactors, Typo/Config Fixes, and Fast-Track Mini-Plans adhering to Pedantry vs Mastery (Pólya, 1945, p. 148, 171) and Lazy Senior Dev Minimalism (The Decision Ladder, YAGNI, Shortest Diff).

GulajavaMinistudio/awesome-copilot-id · 87 tokens

spec-ship