release-ship SKILL.md skillB
release-ship from philoserf/claude-code-config is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add philoserf/claude-code-config/release-ship@git:20261028.f35a5bcPins git:20261028.f35a5bc in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- philoserf/claude-code-config
- Path
skills/release-ship/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261028.f35a5bc, committed Oct 28, 2026
- First version recorded
- Oct 26, 2026
- Size
- 18,602 bytes
- Repository stars
- 13
- License
- MIT
Executes the release workflow for a repository after release-gate passes. Use when tagging, cutting, or shipping a release. Follows the prep-PR pattern: version bump, CHANGELOG, and walkthrough ship in one PR before tagging.
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
# Release Final step in the release pipeline. Assumes `release-gate` has already passed and the target version has been decided. This skill follows the **prep-PR pattern**: version bump + CHANGELOG + walkthrough ship as one atomic PR. The tag is applied **after merge**, pointing at the merged commit. Never use a tool that bumps and tags in one step (`npm version`, `bun version`, `hatch version --tag`) — they tag immediately and skip the CHANGELOG and walkthrough entirely. The workflow is a single linear pass — run the phases in order: 0. Read the plan → 1. Prep branch → 2. Version bump → 3. CHANGELOG → 4. Walkthrough → 5. Build, commit & open PR → **(merge)** → 6. Gate, then tag → 7. Push tag → 8. Release notes → 9. Deploy → 10. Verify ## Prerequisites Before starting, confirm: - `release-gate` passed with no FAIL status, **or** exited `3` (NOT STARTED), which is the normal state before a release: it means the current version is already tagged and phases 1-5 below are exactly what it is asking for. Phase 6 re-runs the gate itself and requires exit `0` — that check is a step in the workflow, not a precondition to remember. …
Read the whole file at its exact version.
How to install
mdr add philoserf/claude-code-config/release-ship@sha256:463960487c8eb1acThe line at the top of this page pins the label git:20261028.f35a5bc, 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_gjethuzijb6od3ty)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 26, 2026 and Oct 28, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261028.f35a5bc latest | 2026-10-28 | f35a5bc | 18,602 B | B | view · diff |
| git:20261026.7b9ba83 | 2026-10-26 | 7b9ba83 | 18,369 B | B | view · diff |
| git:20261026.65ec569 | 2026-10-26 | 65ec569 | 18,169 B | B | view · diff |
| git:20261026.7d73f1a | 2026-10-26 | 7d73f1a | 18,169 B | B | view · diff |
| git:20261026.04d24cd | 2026-10-26 | 04d24cd | 18,281 B | B | view |
Audit of the latest version
- fail: Frontmatter declares a name
- pass: Frontmatter block present
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (18602 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
philoserf/claude-code-config · 13 stars · license MIT · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gjethuzijb6od3ty GET https://markdownregistry.com/api/v1/resolve?ref=philoserf/claude-code-config/release-ship GET https://markdownregistry.com/api/v1/blob/463960487c8eb1ac6106f2160623075cc7bb034e4528ea8c4235dcebe144f133
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.