agentmods.dev

ship

A workflow for checking, committing, pushing, and opening a GitHub pull request for completed code changes.

In plain words
What is it for?
Use it to inspect changed files, run workspace or full CI checks, create a branch, make a commit, push it, and optionally connect the work to a GitHub issue.
Why use it?
It makes the release steps repeatable and stops when a required check fails, reducing the chance of shipping unverified changes.

Skill for Claude CodeCodex

31 4mo ago A scan 48 tokens original MIT
View the source file JeremyDev87/codingbuddy
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/jeremydev87/codingbuddy/ship
Any agent
npx skills add JeremyDev87/codingbuddy --skill ship
Clone the repo
git clone --depth 1 https://github.com/JeremyDev87/codingbuddy

Made for: Claude Code, Codex.

Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,109 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.

ModelPer sessionOnce invoked
Fable 5 $0.00048 $0.02109
Opus 5 $0.00024 $0.01055
Sonnet 5 $0.00010 $0.00422
Haiku 4.5 $0.00005 $0.00211

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

Security

Grade A, and why

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 2d 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.

.claude/skills/ship/SKILL.md · 262 lines

How it starts

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

Ship Changes

Follow every step in order. Stop and report if any step fails.

Step 1: Parse Arguments and Determine Issue Context

Parse $ARGUMENTS for:

  • --full flag: If present, run ALL workspace checks (matches CI exactly). Remove --full from arguments before processing issue context.
  • Issue context: Remaining argument is an issue number or URL.

Check if issue context is provided:

  • With issue (/ship 613 or /ship --full 613):

    gh issue view <number> --json title,body,labels

    Use the issue title and labels to inform branch name, commit message, and PR description.

  • Without issue (/ship or /ship --full): Skip issue fetch. Derive context entirely from the changed files and git diff. The user will be asked to confirm the commit message and PR title before proceeding.

Step 2: Check Working Tree

git status
git diff --stat

If there are no changes to ship, stop and inform the user.

Step 3: Detect Affected Workspaces

Run git diff --name-only (include both staged and unstaged changes) and classify changed files into workspaces:

Path Pattern Workspace Checks
apps/mcp-server/** codingbuddy lint, format:check, typecheck, test:coverage, circular, build
packages/rules/** codingbuddy + rules-validation Above + ajv-cli validate + markdownlint-cli2
packages/claude-code-plugin/** codingbuddy-claude-plugin lint, format:check, typecheck, test:coverage, circular, build
apps/landing-page/** landing-page lint, format:check, typecheck, test:coverage, check:circular, build
.claude/**, .cursor/**, .antigravity/**, .codex/**, .github/**, scripts/** rules-validation only ajv-cli validate + markdownlint-cli2

Docs-only changes: If changed files don't match any pattern above (e.g., docs-only, root config) AND --full is NOT set, skip all CI checks (including security) and proceed to Step 7.

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

  1. 2d ago First seen · 262 lines · 48 tokens per session scan A dab775d44d9b

Subscribe to this mod's changes

ship is a skill published in the GitHub repository JeremyDev87/codingbuddy (31 stars, last pushed 4mo ago), licensed MIT. It adds 48 tokens to every session and 2,109 once invoked, about $0.0002 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-30.

Code reviewDevOps and cloudGit and workflowai-agentsai-codingai-coding-assistantai-rulesclaude-codetypescript
Related

Other skills, from other repositories

om-integration-builder

Build integration provider packages for the Open Mercato Integration Marketplace (payment, shipping, data-sync, webhook). Scaffolds the npm package, adapter, credentials, widget injection, webhook processing, health checks, i18n, tests. Triggers on "build integration", "add provider", "integrate with…

open-mercato/open-mercato · 73 tokens

om-ds-guardian

Design System Guardian for Open Mercato. Use for frontend UI work, design-system compliance reviews, semantic token migration, hardcoded color or typography cleanup, DS-compliant page scaffolding, and common DS violations such as arbitrary text sizes, raw color classes, or missing shared states. Prefer this skill…

open-mercato/open-mercato · 76 tokens

om-integration-tests

Run and create QA integration tests (Playwright TypeScript), including executing the full suite, converting optional markdown scenarios, and generating new tests from specs or feature descriptions. Defers all environment boot/reuse to the om-prepare-test-env skill and attaches to the shared descriptor it writes. Use…

open-mercato/open-mercato · 99 tokens

om-create-agents-md

Create or rewrite AGENTS.md files for Open Mercato packages and modules. Use this skill when adding a new package, creating a new module, or when an existing AGENTS.md needs to be created or refactored. Ensures prescriptive tone, the Always/Ask First/Never/Validation Commands boundary structure, MUST-style rules…

open-mercato/open-mercato · 85 tokens

om-smart-test

Run only the tests affected by changed code. Use when the user says "run affected tests", "run smart tests", "test only what changed", "run tests for this PR", "run tests for my changes", "selective tests", or asks to run tests without running the full suite.

open-mercato/open-mercato · 64 tokens

om-auto-qa-scenarios

Generate a human QA report for a window of merged PRs (date floor, PR-number floor, or default last 7 days) and ship it as a docs-only PR against develop. Groups work into P0/P1/P2 testing routes with click paths, verification points, and risk callouts. Writes markdown + HTML under .ai/analysis/. Hands off to…

open-mercato/open-mercato · 99 tokens