release
Skill159 starsChanged 10 days agoMITView on GitHub
Release a new version of heptabase-cli-skills, the public Agent Skills plugin package for the Heptabase CLI. Use whenever asked to release, publish, ship, tag, or bump the version of this skills package/plugin, to check whether it is release-ready, or to create its GitHub release. Covers version bumping across plugin manifests, preflight validation, tagging, and publishing the GitHub release. Not for releasing the Heptabase desktop app or the heptabase CLI binary itself — those are versioned separately.
- Commits and pushes
193 other projects use a version of this.
Adopted by
Most recently taken up by
- naomiaro/waveform-playlisttheir own version, first seen Nov 16, 2026
- osmlab/name-suggestion-indextheir own version, first seen Nov 16, 2026
- vulnerability-lookup/vulnerability-lookuptheir own version, first seen Nov 16, 2026
- ClickHouse/mcp-clickhousetheir own version, first seen Nov 16, 2026
- bpatrik/pigallery2their own version, first seen Nov 16, 2026
- Shasnow/StarRailAssistanttheir own version, first seen Nov 16, 2026
Used with
Projects with it also use create-agent-adapter, changelog-style and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillcreate-agent-adapter
Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.
Also in 5 projects that use this
GrinvSkillchangelog-style
Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.
Also in 4 projects that use this
GrinvSkilldocs-consistency-check
Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.
Also in 4 projects that use this
Microsoft AzureSkillcomponent-release
Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.
Also in 4 projects that use this
Microsoft AzureSkilldocumentation-consistency
Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.
Also in 8 projects that use this
rivet-devSkilllaunch-graphics
Generate agentOS marketing/launch graphics (launch & social heroes, code-snippet cards) from the committed generators in docs-internal/graphics. Use when asked to make, update, or render an agentOS launch image, social image, "agentOS Apps" graphic, or technical code-snippet image.
Also in 3 projects that use this
- +3 more from Grinv
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 193
- paperclipai/paperclip★ 114ksame name
- modelcontextprotocol/servers★ 92ksame name
- remotion-dev/remotion★ 73ksame name
- traefik/traefik★ 66ksame name
- usememos/memos★ 64ksame name
- tw93/Pake★ 64ksame name
- AmruthPillai/Reactive-Resume★ 46ksame name
- amruthpillai/reactive-resume★ 46ksame name
- reactive-resume/reactive-resume★ 46ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
183 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- maintain-skillsSkill
- public-repo-guardSkill
- heptabase-cliSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 183 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
Run from anywhere inside the repo.
- Distinctive: line 76
If preflight reports FAIL on anything, stop and fix it — do not tag around a failing check.
- Distinctive: line 77
Never tag from a run that withheld the release plan (not tag-ready).
“Common” is measured: kept by at least 6 in 10 of the 183 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Releasing heptabase-cli-skills
This repo ships a public plugin package installed via the Claude Code marketplace, Cursor, npx skills, and OpenCode. Claude Code caches installed plugins by resolved plugin version, so users only receive updates when the version changes — pushing commits without a bump ships nothing.
Conventions (and why)
.claude-plugin/plugin.jsonversionis the single source of truth. Claude Code resolves the version as:plugin.json→marketplace.jsonplugin entry → commit SHA. Never add aversionto amarketplace.jsonplugin entry — it would silently shadow future strategy changes..cursor-plugin/plugin.jsonmust mirror the same version on every release (Cursor reads its version from that file).- Tag format:
vX.Y.Zmatching the manifest version. - CLI compatibility is a minimum version.
metadata.heptabase-cli-version-rangeinskills/heptabase-cli/SKILL.mdis>=X.Y.Z: the oldest CLI that has every command the skill itself names. The skill leaves command details to the CLI's own System Manual and--help, which ship with each CLI, so a newer CLI does not need a new skill release. - GitHub release title:
Compatible with CLI v<minimum> and later, from that range (e.g.>=0.10.0→ "Compatible with CLI v0.10.0 and later"). The title states compatibility, not features, and stays identical across releases with the same minimum. - Release notes are auto-generated from merged PR titles (
--generate-notes). There is no CHANGELOG file. This means changes should land via PRs with clear conventional-commit titles (feat: ...,fix: ...) — the PR title is the changelog entry.
Version bump rules
| Bump | When |
| patch | Documentation-only skill fixes; no CLI compatibility change |
| minor | New CLI commands supported, new non-breaking CLI behavior, or a higher minimum CLI version |
| major | Rare package-level changes only: plugin rename, removing the primary skill, changing the distribution model |
Bundled scripts
Run from anywhere inside the repo; they locate the repo root themselves.
scripts/bump-version.mjs <patch|minor|major|X.Y.Z> [--dry-run]— updates both plugin manifests together (prepares both replacements, writes both, then re-reads to verify). Refuses to run if the manifests are out of sync, the target version does not advance, or a manifest does not contain exactly one"version": "…"needle. Prints JSON. It does NOT touchmetadata.heptabase-cli-version-range— that is a judgment call (step 5).scripts/preflight.mjs [--skip-validators]— read-only release-readiness report: manifest sync, marketplace version rule, CLI range format and consistency (frontmatter vs prose), installed CLI vs the minimum, clean tree, branch, tag availability, version advances past the latest origin tag (falls back to local tags only when origin is unreachable), and the three official validators (skills-ref,claude plugin validate, Cursor manifest). Exits non-zero on any FAIL. Prints the exact release-plan commands only when tag-ready: no FAILs, clean tree, onmain, not behindorigin/main, and validators were not skipped. On a feature branch it may still pass with no FAILs and tell you to land the PR first.
Release process
- Review what shipped since the last release to choose the bump:
git log $(git describe --tags --abbrev=0)..HEAD --oneline gh pr list --state merged --limit 20 - Decide the bump type using the rules above. If the changes span categories, the highest category wins. Confirm with the maintainer when ambiguous.
- Create a feature branch from updated
main(do not bump or commit release changes directly onmain):git checkout main && git pull git checkout -b release/vX.Y.Z - Bump the version:
node .claude/skills/release/scripts/bump-version.mjs patch - Only if the skill now names a command or behavior that older CLIs lack: raise the minimum in
metadata.heptabase-cli-version-rangeinskills/heptabase-cli/SKILL.md(e.g.>=0.10.0→>=0.12.0), in both the frontmatter and the prose sentence under Prerequisites that repeats it. Preflight verifies they agree. A newer CLI alone is not a reason to raise it. - Commit the bump (and any CLI-range edit). Preflight requires a clean tree, so do not run it against uncommitted manifest edits.
- Run preflight and fix any FAILs:
On a feature branch,node .claude/skills/release/scripts/preflight.mjson-mainis a WARN and the release plan is withheld — that is expected before the PR merges. - Land the changes via a PR with a conventional-commit title (it becomes the release-notes entry). CI runs the same three validators. Wait for merge.
- On updated main, pull, rerun preflight (it should now be tag-ready and print the release plan), then tag — this is public, so ask the maintainer for explicit confirmation first:
git tag vX.Y.Z && git push origin vX.Y.Z - Publish the GitHub release — again only with explicit confirmation. Use the exact command from preflight's release plan; it looks like:
gh release create vX.Y.Z --title "Compatible with CLI v0.10.0 and later" --generate-notes - Verify:
gh release view vX.Y.Z. Installed users pick it up through the plugin update flows documented in README.md.
Safety
- Tagging, pushing tags, and publishing releases are public and effectively irreversible. Never run steps 9–10 without the maintainer's explicit go-ahead in the current conversation, and never batch them silently with other work.
- If preflight reports FAIL on anything, stop and fix it — do not tag around a failing check.
- Never tag from a run that withheld the release plan (not tag-ready).
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.

