Home / khaledsaeed18 / dotclaude · GitHub

release-tag SKILL.md skillA

release-tag from khaledsaeed18/dotclaude is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add khaledsaeed18/dotclaude/release-tag@git:20260608.0cc2133

Pins git:20260608.0cc2133 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: khaledsaeed18/dotclaude
Path: skills/version-control/release-tag/SKILL.md
Versions recorded: 2
Latest version: git:20260608.0cc2133, committed Jun 8, 2026
First version recorded: Jun 6, 2026
Size: 5,140 bytes
Repository stars: 5
License: MIT

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.

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

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

The exact contents, by fingerprint

mdr add khaledsaeed18/dotclaude/release-tag@sha256:90ee5db569740715

The line at the top of this page pins the label git:20260608.0cc2133, 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.

Badge

[![mdr](https://markdownregistry.com/badge/art_tb5ta6awlvibv3lp.svg)](https://markdownregistry.com/a/art_tb5ta6awlvibv3lp)

4 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 2 versions of this file, between Jun 6, 2026 and Jun 8, 2026, about one every 2 days.

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

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

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

GitHub

khaledsaeed18/dotclaude · 5 stars · license MIT · pushed 2026-11-05 · 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 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 khaledsaeed18/dotclaude

improve SKILL.md skill

khaledsaeed18/dotclaude · .agents/skills/improve/SKILL.md · Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER…

v1.0.0 · audit B · 5 stars

coolify-image-app SKILL.md skill

khaledsaeed18/dotclaude · .claude-plugin/plugins/deploy/skills/coolify-image-app/SKILL.md · Create and configure a Coolify application that runs a prebuilt image from a registry. Use when adding an app to…