Install the "release" agent skill from https://github.com/heptameta/heptabase-cli-skills/tree/main/.claude/skills/release into .claude/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add heptameta/heptabase-cli-skills --skill release -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "release" agent skill from https://github.com/heptameta/heptabase-cli-skills/tree/main/.claude/skills/release into .agents/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add heptameta/heptabase-cli-skills --skill release -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "release" agent skill from https://github.com/heptameta/heptabase-cli-skills/tree/main/.claude/skills/release into .cursor/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add heptameta/heptabase-cli-skills --skill release -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "release" agent skill from https://github.com/heptameta/heptabase-cli-skills/tree/main/.claude/skills/release into .gemini/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add heptameta/heptabase-cli-skills --skill release -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "release" agent skill from https://github.com/heptameta/heptabase-cli-skills/tree/main/.claude/skills/release into .github/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add heptameta/heptabase-cli-skills --skill release -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "release" agent skill from https://github.com/heptameta/heptabase-cli-skills/tree/main/.claude/skills/release into .opencode/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
release
GitHub stars
155
Token cost
~1.6k tokens
SKILL.md length
702 words
Files
4 (incl. scripts)
Skills in repo
4
Repo updated
First seen
Licence
MIT
At a glance
Release a new version of heptabase-cli-skills, the public Agent Skills plugin package for the Heptabase CLI.
Works in 11 steps: Review what shipped since the last… → Decide the bump type using the rules… → Create a feature branch from updated… → …
Asked to release
SKILL.md covers Conventions (and why), Version bump rules, Bundled scripts and Release process, plus 1 more section
Runs JavaScript scripts from its folder; calls git, gh and node
What it does
Release is an agent skill from heptameta/heptabase-cli-skills. 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.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts (for example `agents/openai.yaml`).
It sits in Development. It works with GitHub. The repository describes itself as: Agent skills for Heptabase CLI. The licence is MIT.
When your agent uses it
Asked to release
Bump the version of this skills package/plugin
Check whether it is release-ready
Create its GitHub release
Example prompts
“/release”
Requirements
Node.js
Pre-approved tools (allowed-tools): Bash(node *), Bash(npx --yes skills-ref *), Bash(git status *), Bash(git log *), Bash(git tag -l *), Bash(git describe *), Bash(git rev-parse *), Bash(gh release list *), Bash(gh release view *), Bash(gh pr list *)
Workflow steps
11 steps, taken from the first numbered list in SKILL.md.
1Review what shipped since the last release to choose the bump
2Decide the bump type using the rules above. If the changes span categories, the highest category wins. Confirm with the maintainer when…
3Create a feature branch from updated main (do not bump or commit release changes directly on main)
4Bump the version
5Only if the supported CLI range changed (e.g. CLI 0.4.x → 0.5.x): update metadata.heptabase-cli-version-range in…
6Commit the bump (and any CLI-range edit). Preflight requires a clean tree, so do not run it against uncommitted manifest edits.
7Run preflight and fix any FAILs
8Land the changes via a PR with a conventional-commit title (it becomes the release-notes entry). CI runs the same three validators. Wait…
9On updated main, pull, rerun preflight (it should now be tag-ready and print the release plan), then tag — this is public, so ask the…
10Publish the GitHub release — again only with explicit confirmation. Use the exact command from preflight's release plan; it looks like
11Verify: gh release view vX.Y.Z. Installed users pick it up through the plugin update flows documented in README.md.
What it can do on your machine
Read from SKILL.md and the folder at commit b5fb23f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Bash(node *)
Bash(npx --yes skills-ref *)
Bash(git status *)
Bash(git log *)
Bash(git tag -l *)
Bash(git describe *)
Bash(git rev-parse *)
Bash(gh release list *)
Bash(gh release view *)
Bash(gh pr list *)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 2 files in scripts/ (JavaScript), which the agent can run.
Shell commands in SKILL.md call:
git
gh
node
npx
claude
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, gh and npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Release loads about 1.6k tokens when it runs. Until then it costs about 129 tokens; SKILL.md has 702 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~129
When it runs· the whole SKILL.md, loaded when a task matches
~1.6k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
Download SKILL.mdSave it as .claude/skills/release/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
release
description
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.
allowed-tools
Bash(node *), Bash(npx --yes skills-ref *), Bash(git status *), Bash(git log *), Bash(git tag -l *), Bash(git describe *), Bash(git rev-parse *), Bash(gh release list *), Bash(gh release view *), Bash(gh pr list *)
disable-model-invocation
true
metadata.internal
true
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.jsonversion is the single source of truth. Claude Code resolves the version as: plugin.json → marketplace.json plugin entry → commit SHA. Never add a version to a marketplace.json plugin entry — it would silently shadow future strategy changes.
.cursor-plugin/plugin.json must mirror the same version on every release (Cursor reads its version from that file).
Tag format:vX.Y.Z matching the manifest version.
GitHub release title:Compatible with CLI v<range>, where <range> is metadata.heptabase-cli-version-range from skills/heptabase-cli/SKILL.md (e.g. 0.4.x → "Compatible with CLI v0.4.x"). The title states compatibility, not features, and stays identical across releases in the same CLI range.
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 new CLI compatibility range
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 touch metadata.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 consistency (frontmatter vs prose), installed CLI vs declared range, 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, on main, not behind origin/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.
Show full SKILL.md (352 more words)Show less
Release process
Review what shipped since the last release to choose the bump:bash
Only if the supported CLI range changed (e.g. CLI 0.4.x → 0.5.x): update metadata.heptabase-cli-version-range in skills/heptabase-cli/SKILL.md — in both the frontmatter and the prose sentence under Prerequisites that repeats the range. Preflight verifies they agree.
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:bash
node .claude/skills/release/scripts/preflight.mjs
On a feature branch, on-main is 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:bash
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:bash
gh release create vX.Y.Z --title "Compatible with CLI v0.4.x" --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).
Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
Release a new version of heptabase-cli-skills, the public Agent Skills plugin package for the Heptabase CLI. Release is an agent skill from heptameta/heptabase-cli-skills. Release a new version of heptabase-cli-skills, the public Agent Skills plugin package for the Heptabase CLI.
When should I use Release?
Release fits situations like: asked to release; bump the version of this skills package/plugin; check whether it is release-ready; create its GitHub release.
How do I install Release in Claude Code?
Run `npx skills add heptameta/heptabase-cli-skills --skill release -a claude-code`. Or copy the skill folder (.claude/skills/release in heptameta/heptabase-cli-skills) into .claude/skills/release in your project. Claude Code loads it when a task matches its description.
How do I install Release in Codex?
Run `npx skills add heptameta/heptabase-cli-skills --skill release -a codex`. Or copy the skill folder (.claude/skills/release in heptameta/heptabase-cli-skills) into .agents/skills/release in your project. Codex loads it when a task matches its description.
Can I use Release in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add heptameta/heptabase-cli-skills --skill release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release, .gemini/skills/release, .github/skills/release and .opencode/skills/release in your project.
What does Release need to run?
Going by SKILL.md and its folder, Release needs JavaScript for the scripts in its folder and the command-line tools its instructions call (git, gh, node, npx and claude). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Bash(node *), Bash(npx --yes skills-ref *), Bash(git status *), Bash(git log *), Bash(git tag -l *), Bash(git describe *), Bash(git rev-parse *), Bash(gh release list *), Bash(gh release view *), Bash(gh pr list *).
Does Release access the network?
SKILL.md contains no URLs. Its commands use git, gh and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Release safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Release use?
Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Release use?
About 1.6k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Release?
Skills that share tags, products or a category with Release: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Greploop (onyx-dot-app/onyx, 32k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Setup Matt Pocock Skills (bestofjs/bestofjs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release?
heptameta (a GitHub organization) maintains it in heptameta/heptabase-cli-skills, which has 155 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 7, 2026.
