ship SKILL.md skillA
ship from jcottam/agent-resources is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jcottam/agent-resources/ship@v1.6.0Pins v1.6.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jcottam/agent-resources
- Path
skills/engineering/ship/SKILL.md- Versions recorded
- 5
- Latest version
- v1.6.0, committed Oct 19, 2026
- First version recorded
- May 16, 2026
- Size
- 15,743 bytes
- Repository stars
- 21
- License
- MIT
Validate a branch, run quality gates, update documentation and changelog, and open a pull request. Supports GitHub (primary) and Azure DevOps (secondary). Designed for JavaScript/TypeScript projects; quality gate detection requires package.json. Use when the user says "ship", "ship this", "open a PR", "prepare a PR", "send this for review", "let's ship it", or any variation of wanting to finalize work and create a pull request.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Ship Pre-flight checklist that validates the branch, runs quality gates, updates documentation and changelog, and opens a pull request. **GitHub is the primary host; Azure DevOps is secondary.** The scripts detect the provider from the git remote (`github.com` vs `dev.azure.com`). If `origin` is not a GitHub remote, do not use `gh` — even when the remote is ambiguous or a script falls back to GitHub. ## Workflow overview ``` - [ ] Step 0: Defer to the repository (repo ship skill; skip gh if origin is not GitHub) - [ ] Step 1: Verify CLI tools and host auth (GitHub or Azure DevOps) - [ ] Step 2: Preflight (rebase, branch, existing PR, provider) - [ ] Step 3: Quality gates (lint → typecheck → test → build) - [ ] Step 4: Documentation (README.md, AGENTS.md) - [ ] Step 5: Changelog bump - [ ] Step 6: Push and open or update PR - [ ] Step 7: Post-flight report ``` ## Script path placeholder `$SCRIPTS` is a **placeholder** for the absolute path to the `scripts/` directory next to this file — not a predefined shell or PowerShell variable. Resolve it before running any command: - **bash/zsh**: `SCRIPTS=/abs/path/to/scripts` - **PowerShell**: `$SCRIPTS = 'C:\abs\path\to\scripts'` …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_khwkz42fhojjdxn5/e617920622338c88dc6c2b5b5d63d54d894eee57028b14d17ebe6ae33c9c8158.json
Then /plugin install ship@markdownregistry-khwkz42fhojjdxn5 in Claude Code. It installs v1.6.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add jcottam/agent-resources/ship@sha256:e617920622338c88The line at the top of this page pins the label v1.6.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_khwkz42fhojjdxn5)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in jcottam/agent-resources/ship since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of ship from somewhere else? Ask it: where did my ship come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between May 16, 2026 and Oct 19, 2026, about one every 39 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.6.0 latest | 2026-10-19 | aa67033 | 15,743 B | A | view · diff |
| v1.6.0 | 2026-10-08 | d6df699 | 15,720 B | A | view · diff |
| v1.5.0 | 2026-06-29 | cd17c8c | 14,609 B | A | view · diff |
| v1.4.0 | 2026-06-29 | ee322f4 | 13,381 B | A | view · diff |
| v1.2.0 | 2026-05-16 | 22c7f0c | 9,740 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/ship/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (15743 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
jcottam/agent-resources · 21 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_khwkz42fhojjdxn5 GET https://markdownregistry.com/api/v1/resolve?ref=jcottam/agent-resources/ship GET https://markdownregistry.com/api/v1/blob/e617920622338c88dc6c2b5b5d63d54d894eee57028b14d17ebe6ae33c9c8158
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from jcottam/agent-resources
Every file in jcottam/agent-resources