A release procedure for the dot repository, which is a collection of command-line tools and configuration files. It turns Git commit history into a versioned release with a changelog, tag, and publication trigger.

Use it to check release prerequisites, calculate the next semantic version, run the repository checks, publish the release tag, and verify publication.

It coordinates versioning, checks, commits, tags, and pushes so a release is not cut from an unverified or outdated branch.

How fmind/dot configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to fmind/dot. 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/fmind/dot/main/.agents/skills/dot-release/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/fmind/dot

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/fmind/dot/dot-release/github.svg)](https://agentmods.dev/skills/fmind/dot/dot-release)

Your own site

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

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

When invoked 1,322 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.00021	$0.01322
Opus 5.5	$0.00008	$0.00529
Sonnet 5.5	$0.00004	$0.00264
Haiku 4.5	$0.00002	$0.00132

Measured 4d ago against content hash 3229701c846b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

dot-release 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 4d ago.

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/dot-release/SKILL.md · 50 lines

How it starts

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

Dot Release

Use the checkout's release task as the single owner of preparation and publication. The global release guide owns generic versioning and publication verification; this skill owns dot's preconditions and recovery.

Workflow

Confirm authority: the release command commits, pushes, and refreshes the installed CLI. An explicit /dot-release invocation or release request authorizes the whole flow below, including verification fixes, commits, the push to main, and the delivery fixes and follow-up release below; loading this skill for reference, review, or reconciling a past release does not.
Qualify first: run dot-verify on the checkout and resolve its findings. Stop and report instead of releasing when a finding needs the user's decision or a gate stays red.
Commit the candidate: group verified work into logical Conventional Commits (the changelog is generated from them), then git fetch and push main so HEAD equals upstream; pre-push hooks rerun the network checks and tests. If upstream moved, integrate it without rewriting history only when its commits do not overlap the candidate; otherwise stop.
Know the preconditions: the task stops before writing unless dprint, git, git-cliff, mise, and uv exist, the tree is clean on main, HEAD equals the fetched origin/main, and the next tag is absent locally; without new Conventional Commits it releases nothing. Preserve unrelated work when a precondition fails.
Run the owner: use the commands below from the repository; the task runs from source (uv run --frozen --directory dot python -m dot_tasks.release), not the possibly stale installed CLI.
Read the result: the task bumps dot/pyproject.toml, CHANGELOG.md, and dot/uv.lock (only those files may change), formats the changelog with dprint (CD rejects a tree its formatter changes, so this never depends on Git hooks), gates the bumped commit (check:network, which refreshes the vulnerability data CD rechecks, test:starters, which re-resolves unlocked upstream packages since CI ran, build, and the host-only check:completions), then commits with the Lefthook output visible, tags, pushes both with git push --atomic, and runs mise run deploy.
Verify delivery: the tag triggers cd.yml: a read-only gate job reruns mise run all and extracts the git-cliff notes; a publish job holding only contents: write, with no checkout, creates the GitHub release. Confirm with gh run list --workflow cd.yml --branch <tag> and gh release view <tag>. Local command success does not prove CD completion.
Monitor and fix CI/CD: watch the release commit's CI run (including the macOS job) and the tag's CD run to completion with gh run watch <id> --exit-status. On failure, read gh run view <id> --log-failed, fix the root cause forward on main (never rerun to hide a flake), push, and watch CI again; a failed CD gate then needs the next release per Recovery. Repeat until CI is green and gh release view <tag> succeeds; stop and report when a fix needs the user's decision.

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

4d ago Changed 3229701c846b
7d ago Changed d46bac53400b
15d ago Changed e721473d8d26
19d ago Changed · +1 lines 58b75d37cdb5
21d ago Changed · +1 lines 223c663fd71f
23d ago Changed 045086bcf684
24d ago Changed · -1 lines d7701893725e
1mo ago Changed · +2 lines 73f606589db0
1mo ago Changed a4a1946981ca
1mo ago First seen · 47 lines · 21 tokens per session scan A d93690fffd61

Subscribe to this mod's changes

dot-release is a skill published in the GitHub repository fmind/dot (12 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 1,322 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-09-03.

CI and CD Claude Code DevOps and cloud Git and workflow Releases ai-agents chezmoi dotfiles fish-shell mise

sync-release

Owns release-pipeline conventions: sr.yaml schema, the sr CLI verbs (init/plan/prepare/ release) and urmzd/sr action, typed publishers (cargo/npm/pypi/docker/go/custom), monorepo workspace discovery, versionfiles/stagefiles mapping, and post-release patterns. Language-specific build targets live in scaffold-rust…

urmzd/dotfiles · 136 tokens

setup-ci

Defines GitHub Actions workflow structure: ci.yml + release.yml naming, concurrency groups, bot-commit skip, workflowcall reuse, App-token checkout, and optional fsrc/teasr steps. Language-specific pipelines live in scaffold-rust, scaffold-go, scaffold-python, scaffold-node, scaffold-terraform. Use when setting up…

urmzd/dotfiles · 119 tokens

release

Cut or verify a versioned release — bump semver, generate the changelog with git-cliff, tag and publish on GitHub, or reconcile an already-published tag and assets.

fmind/dotfiles · 40 tokens

ship

Push, open a PR, and watch CI; land mode merges and cleans branches. Triggers "ship it", "create PR", "babysit CI", "land it", "fix CI and merge".

darkroomengineering/cc-settings · 45 tokens

release-audit

Audit GitHub releases, git tags, and release assets for one repo or every repo in a directory. Flags orphaned tags, missing binaries/checksums, draft releases, floating tag drift, pre-release remnants, and (when sr.yaml is present) sr config issues. Read-only: never deletes or modifies tags/releases. Use when checking…

urmzd/dotfiles · 126 tokens

repo-init

End-to-end repo bootstrap: creates the GitHub repo (gh repo create), adds an Apache-2.0 LICENSE, dispatches to scaffold-project for CI/release/config, invokes community-health, writes a README, sets topics/description, and makes the initial commit and push. Use when starting a brand-new project from zero and you need…

urmzd/dotfiles · 107 tokens

dot: Skill for Claude Code