preparing-releases
Skill14 starsChanged 32 days agoApache-2.0View on GitHub
Use when preparing, validating, tagging, or publishing a KamehaDB desktop release, including version bumps, release changelogs, release artifacts, and GitHub release workflow checks.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- landing/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- brainstorm-featureSkill
- bump-versionSkill
- context-handoffSkill
- document-wikiSkill
- estimate-featureSkill
- implement-taskSkill
- lean-auditSkill
- plan-featureSkill
- read-codebase-contextSkill
- review-and-verifySkill
- setup-codebaseSkill
- setup-openezSkill
- systematic-debuggingSkill
- using-devkitSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Verify release scope and quality:
- Very specific: line 26
Run go test ./... after Go backend changes.
- Distinctive: line 34
Do not claim a release is ready without fresh command output from the checklist.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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/remotev*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-versionto update exactly the root, desktop, and sharedpackage.jsonfiles. Never updatelanding/package.json. - Turn
[Unreleased]intovX.Y.Zwith 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, andREADME.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 --checkRun
go test ./...after Go backend changes. Runnpm --prefix landing run buildafter 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.appzip, 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

