A release workflow that takes a code branch through checks and prepares a pull request for automatic merging. It covers repository status, authentication, verification, review of the full change, and merge-queue requirements.

Use it when asked to ship changes: check the branch, run strict verification, compare failures with the main branch, document pre-existing or flaky failures, and make the pull request ready.

It provides a repeatable path from local changes to a reviewed, verified pull request. It also keeps test failures classified instead of hiding them by weakening tests or changing timeouts.

How KeepSoftwareSimple/compass-calendar configures Claude Code and Cod

Reuse

Borrowing it

Nothing to install: this file belongs to KeepSoftwareSimple/compass-calendar. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/KeepSoftwareSimple/compass-calendar/main/.agents/skills/ship/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/KeepSoftwareSimple/compass-calendar

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/keepsoftwaresimple/compass-calendar/ship/github.svg)](https://agentmods.dev/skills/keepsoftwaresimple/compass-calendar/ship)

Your own site

<a href="https://agentmods.dev/skills/keepsoftwaresimple/compass-calendar/ship"><img src="https://agentmods.dev/badge/skills/keepsoftwaresimple/compass-calendar/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/keepsoftwaresimple/compass-calendar/ship"><img src="https://agentmods.dev/badge/skills/keepsoftwaresimple/compass-calendar/ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 854 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.00036	$0.00854
Opus 5.5	$0.00014	$0.00342
Sonnet 5.5	$0.00007	$0.00171
Haiku 4.5	$0.00004	$0.00085

Measured yesterday against content hash 554a064eb847, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 yesterday.

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.

.agents/skills/ship/SKILL.md · 67 lines

How it starts

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

Ship

Status lives on the GitHub issue (labels, open PR, closed state). Nothing in the repo records it.

Steps

Preflight. git status; work on a branch off origin/main, never on main; gh auth status; find any existing PR for the branch.
Verify. bun run verify --strict. Fix failures and rerun, at most two retries. VERDICT: INCOMPLETE means Chromium is missing: run bunx playwright install chromium and rerun. Never weaken a test, widen a timeout, or change test order to get there.

The local verdict is evidence; CI is the gate. When test:web, test:a11y, or test:e2e fails, verify reruns the failing files on the branch and on origin/main in a temporary worktree and prints a Baseline against origin/main: block that sorts each failure into NEW (fails only on the branch), PRE-EXISTING (fails on main too), or FLAKY (passed on rerun). Only NEW failures make the verdict FAIL; fix those. Paste the PRE-EXISTING and FLAKY lists into the PR body as-is. A failure verify cannot classify (a crash, an error outside a test) stays FAIL; show why it is environmental in the PR or treat it as real.
Self-check. Read the complete base-to-head diff as a stranger would: state, races, cleanup, keyboard and focus paths, accessibility, auth, data loss. If the diff added more than a screen of new abstraction, run the simplify skill. Confirmed problems become isolated fix commits, then rerun step 2.
PR. Open a draft PR against main using .github/PULL_REQUEST_TEMPLATE.md: Fixes #N, what changed and why, the pasted VERDICT: line and checks run. No unchecked manual-testing boxes. Mark it ready once step 2 is satisfied; reviews run on ready PRs only, so a draft that never becomes ready is a stop, not a handoff.
Merge. Mark the PR ready and run gh pr merge --auto. main takes changes only through the merge queue, so a direct merge is refused by rule; GitHub squash-merges through the queue once required checks pass. No label is involved. The required checks are the whole gate: no line-count rail, no path denylist, nothing to look for or wait on.

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

yesterday First seen · 67 lines · 36 tokens per session scan A 554a064eb847

Subscribe to this mod's changes

ship is a skill published in the GitHub repository KeepSoftwareSimple/compass-calendar (226 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 854 once invoked, about $0.0001 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-11-07.

Git and workflow React Releases Testing TypeScript calendar google google-calendar nodejs

ship next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
shipKeepSoftwareSimple/compass-calendar	Skill	226	today	MIT	A	36	Claude Code, Codex
draft-release-notesprisma/orm	Skill	48k	yesterday	Apache-2.0	A	174	Claude Code, Codex
publish-npm-versionprisma/orm	Skill	48k	yesterday	Apache-2.0	A	182	Claude Code, Codex
merge-seedkriasoft/react-starter-kit	Skill	24k	6d ago	MIT	A	49	Claude Code, Codex
deployment-proceduresDDS-Solutions/AI-TadPole-OS	Skill	8	2d ago	MIT	A	29	Claude Code
githubDaleStudy/skills	Skill	4	3d ago	MIT	A	133	Claude Code
create-prprisma/orm	Skill	48k	yesterday	Apache-2.0	A	48	Claude Code, Codex

compass-calendar: Skill for Claude Code