release-tag skillA
release-tag is agent-read markdown (skill) from khaledsaeed18/dotclaude: Cut a release by determining the SemVer bump from history, updating version files across any stack, refreshing the changelog, creating an annotated (optionally signed) Git tag, and pushing the release safely after pre-flight checks. Use when tagging a version, bumping the version, or preparing a release..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
Take the repo from "ready" to a clean, tagged, pushed release. Releases are outward-facing and effectively irreversible once published, so every step is gated by pre-flight checks and explicit confirmation. ## Hard rules: never break these - **Never release a dirty or unverified tree.** Working tree clean, on the correct branch, up to date with the remote, and tests/CI green; all true before tagging. - **Tags are immutable once published.** Never move or overwrite a pushed tag; if a release is wrong, cut a new patch version. Force-retagging breaks everyone who already pulled. - **Follow SemVer honestly.** The bump must reflect what actually changed (see Step 2), not a convenient number. - **Confirm before the commit, the tag, and the push.** These are the irreversible, outward-facing actions. - **No AI/co-author trailers** in the release commit or tag message. - **Publishing is downstream.** Tagging ≠ publishing to a registry. Don't run `npm publish` / `cargo publish` / etc. unless explicitly asked; most pipelines publish from CI on tag. ## Step 1: Pre-flight - `git status` → clean tree (or stash/commit deliberate changes first). …
Read the whole file at its exact version.
How to install
mdr add khaledsaeed18/dotclaude/release-tag@git:20260608.0cc2133mdr add khaledsaeed18/dotclaude/release-tag@sha256:90ee5db569740715Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_tb5ta6awlvibv3lp)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260608.0cc2133 latest | 2026-06-08 | 0cc2133 | 5,140 B | A | view · diff |
| git:20260606.7d504a8 | 2026-06-06 | 7d504a8 | 5,183 B | A | view |
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 (5140 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
khaledsaeed18/dotclaude · 5 stars · license MIT · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_tb5ta6awlvibv3lp GET https://markdownregistry.com/api/v1/resolve?ref=khaledsaeed18/dotclaude/release-tag GET https://markdownregistry.com/api/v1/blob/90ee5db569740715e3de5f3ff0d7e5a5d94c46fae24b885a4b37a4bd453b941d
Your agent 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.
More from khaledsaeed18/dotclaude
Every file in khaledsaeed18/dotclaude