What is preparing-releases?

A release-preparation workflow for KamehaDB desktop software, covering version updates, release notes, build files, and GitHub release checks.

Checking changes and tags, updating the app version, preparing changelogs, checking release artifacts and workflows, and running required tests and type checks.

It reduces mistakes when preparing a release and prevents publishing when the worktree, version, or release scope is inconsistent.

How asta-nguyen/kamehadb configures Codex

Reuse

Borrowing it

Nothing to install: this file belongs to asta-nguyen/kamehadb. 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/asta-nguyen/kamehadb/main/.agents/skills/preparing-releases/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/asta-nguyen/kamehadb

Made for: 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/asta-nguyen/kamehadb/preparing-releases/github.svg)](https://agentmods.dev/skills/asta-nguyen/kamehadb/preparing-releases)

Your own site

<a href="https://agentmods.dev/skills/asta-nguyen/kamehadb/preparing-releases"><img src="https://agentmods.dev/badge/skills/asta-nguyen/kamehadb/preparing-releases/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/asta-nguyen/kamehadb/preparing-releases"><img src="https://agentmods.dev/badge/skills/asta-nguyen/kamehadb/preparing-releases.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 507 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.00041	$0.00507
Opus 5.5	$0.00016	$0.00203
Sonnet 5.5	$0.00008	$0.00101
Haiku 4.5	$0.00004	$0.00051

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

Security

Grade A, and why

preparing-releases 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 19d 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/preparing-releases/SKILL.md · 35 lines

How it starts

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

Preparing Releases

Prepare a releasable commit first. Tag, push, and publish only with direct user instruction.

Release checklist

Inspect git status --short, the intended diff, local/remote v* tags, and all three app-version files. If the worktree has unrelated changes or an existing tag conflicts with a manifest version, stop and ask for the intended release scope/version; never move or reuse an existing tag.
Confirm the SemVer target with the user. Use bump-version to update exactly the root, desktop, and shared package.json files. Never update landing/package.json.
Turn [Unreleased] into vX.Y.Z with today’s date and add a fresh [Unreleased]. Keep entries concise and user-facing; remove empty, duplicate, dependency-only, and internal implementation notes.
For new engines, major workflows, or product-description changes, update the five public surfaces in AGENTS.md: landing hero, landing metadata, OG card, compare screenshots, and README.md. Regenerate visual assets only when their source changed.
Verify release scope and quality:
```
pnpm typecheck
pnpm --filter @kamehadb/desktop test
pnpm test:go
pnpm build
git diff --check
```
Run go test ./... after Go backend changes. Run npm --prefix landing run build after landing or README changes. Confirm all three versions are identical and stage only intentional release files.
Request explicit approval before committing, pushing, creating vX.Y.Z, or triggering/publishing any release. After an explicitly authorized pushed tag, monitor .github/workflows/release.yml: it creates a draft release with a macOS universal .app zip, a Windows .exe, and a Linux amd64 tarball. Publish the draft only with explicit final approval.

Guardrails

A release tag is immutable: correct the next version instead of force-moving an existing tag.
A dirty worktree is not a release candidate until its unrelated changes are separated or approved.
Do not claim a release is ready without fresh command output from the checklist.

Read the full file on GitHub · 35 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

agents/openai.yaml 191 B

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.

19d ago Changed · +1 lines a848f8490203
2mo ago First seen · 34 lines · 41 tokens per session scan A 039663e86e0f

Subscribe to this mod's changes

preparing-releases is a skill published in the GitHub repository asta-nguyen/kamehadb (14 stars, last pushed 10d ago), licensed Apache-2.0. It adds 41 tokens to every session and 507 once invoked, about $0.0002 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-08-30.

Databases Git and workflow LLM Productivity ai database-management free tools

preparing-releases next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
preparing-releasesasta-nguyen/kamehadb	Skill	14	10d ago	Apache-2.0	A	41	Codex
releasematrixorigin/memoria	Skill	623	2d ago	Apache-2.0	A	27	Claude Code, Codex
product-multi-role-analysisdigoal/blog	Skill	8.6k	2d ago	GPL-2.0	A	113	Codex
dlt-connectorCanner/WrenAI	Skill	18k	2d ago	none	A	158	Claude Code, Codex
wrenCanner/WrenAI	Skill	18k	2d ago	none	A	315	Claude Code
git-expertpersonamanagmentlayer/pcl	Skill	44	11d ago	Apache-2.0	A	57	Claude Code
open-pr-menubarTOMOSIA-VIETNAM/open-pr	Skill	45	yesterday	MIT	A	43	Cursor

kamehadb: Skill for Codex