A workflow for preparing software changes for delivery: it formats and checks the code, runs tests, updates the changelog, creates a conventional commit, pushes it, and updates the pull request.

Use it when you want to run the pre-commit checks and then commit, push, update the pull request, and suggest reviewers.

It puts the common release steps in one repeatable process and stops when required verification fails.

ship-it — Skill for Claude Code and Codex by paultyng: A workflow for preparing software changes for delivery: it…

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.

agentmods

npx agentmods add skills/paultyng/skill-issue/ship-it

Any agent

npx skills add paultyng/skill-issue --skill ship-it

Clone the repo

git clone --depth 1 https://github.com/paultyng/skill-issue

Made for: Claude Code, Codex.

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/paultyng/skill-issue/ship-it.svg)](https://agentmods.dev/skills/paultyng/skill-issue/ship-it)

Your own site

<a href="https://agentmods.dev/skills/paultyng/skill-issue/ship-it"><img src="https://agentmods.dev/badge/skills/paultyng/skill-issue/ship-it.svg" alt="Measured on agentmods" height="20"></a>

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

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

Security scan A 0 findings. Scan, not verified.

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	$0.00063	$0.01000
Opus 5	$0.00032	$0.00500
Sonnet 5	$0.00013	$0.00200
Haiku 4.5	$0.00006	$0.00100

Measured 5d ago against content hash b6917481ac31, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ship-it 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 5d 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/ship-it/SKILL.md · 84 lines

How it starts

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

Ship It

Run the full pre-commit pipeline, commit, push, and handle PR housekeeping.

1. Verify

Run verification per verify-when-complete. Stop if any step fails.

Review-status check (informational, non-blocking). If a .reviews/<date>/SUMMARY.md exists whose GIT_COMMIT_FULL metadata header matches the current HEAD SHA, count the rows under ## Findings — untracked and inside the <details> block for Findings — tracked, then print a single line:

Review status: <N> untracked / <M> tracked findings @ <short-sha> (<.reviews/path>)

Do not block on N > 0 — /ship-it runs because the user said so. The line is a sanity check, not a gate. If no matching SUMMARY.md exists, skip the line silently (don't run /review-all from here).

2. Changelog

Check if the project has a changelog convention:

If Taskfile.yaml has a changelog task, run task changelog and follow its output.
Otherwise, look for existing changelog entries:
- Per-PR fragment directories like .changeset/ (JS/TS via @changesets/cli), .changes/ (Python via towncrier), or similar project-defined conventions
- CHANGELOG.md at the repo root
If a convention is found, create a terse entry following the existing format and patterns.
If no changelog convention exists, skip this step.

3. Commit

Stage all changes and commit using Conventional Commits format:

<type>[optional scope]: <description>

Common types: feat, fix, refactor, test, docs, chore, ci, build.

Always create a new commit. Never amend.

Apply terse-output commit-message tone: imperative subject ≤72 chars, body explains why (the diff shows what), no "this commit does X" / "I" / "we" / "now". Keep the Co-Authored-By: Claude… attribution.

4. Push and PR

Push the current branch:

git push -u origin HEAD

If a PR exists for the current branch, update its title and description to reflect the current state:

Read the full file on GitHub · 84 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.

5d ago First seen · 84 lines · 63 tokens per session scan A b6917481ac31

Subscribe to this mod's changes

ship-it is a skill published in the GitHub repository paultyng/skill-issue (9 stars, last pushed 24d ago), licensed MIT. It adds 63 tokens to every session and 1,000 once invoked, about $0.0003 per session on Opus 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.

Git and workflow Releases agent-skills ai-tools claude-code cursor dotfiles

deployment-manager

Deployment and release management specialist for CrawlForge MCP Server. Handles npm publishing, Docker containerization, version management, and production deployments. Use before releases, deployments, and version bumps.

mysleekdesigns/crawlforge-mcp · 39 tokens

vibetime-release

Use for VibeTime release work, including bumping the date-based version, creating and pushing release tags, triggering GitHub Actions CI packaging, creating or updating GitHub Releases with notes from the previous version, and verifying uploaded macOS/Windows assets. Trigger on requests such as 发版, 发布新版, release, bump…

BarryYangi/vibetime · 88 tokens

ship-it