agentleFS
heptametaheptameta/heptabase-cli-skills/.claude/skills/release/SKILL.md

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

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.
  • MicrosoftSkill

    create-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

  • GrinvSkill

    changelog-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

  • GrinvSkill

    docs-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 AzureSkill

    component-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 AzureSkill

    documentation-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-devSkill

    launch-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

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
  1. Distinctive:

    Run from anywhere inside the repo.

    line 33
  2. Distinctive:

    If preflight reports FAIL on anything, stop and fix it — do not tag around a failing check.

    line 76
  3. Distinctive:

    Never tag from a run that withheld the release plan (not tag-ready).

    line 77

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.json version 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.
  • CLI compatibility is a minimum version. metadata.heptabase-cli-version-range in skills/heptabase-cli/SKILL.md is >=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

BumpWhen
patchDocumentation-only skill fixes; no CLI compatibility change
minorNew CLI commands supported, new non-breaking CLI behavior, or a higher minimum CLI version
majorRare 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 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, 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.

Release process

  1. 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
  2. Decide the bump type using the rules above. If the changes span categories, the highest category wins. Confirm with the maintainer when ambiguous.
  3. Create a feature branch from updated main (do not bump or commit release changes directly on main):
    git checkout main && git pull
    git checkout -b release/vX.Y.Z
  4. Bump the version:
    node .claude/skills/release/scripts/bump-version.mjs patch
  5. Only if the skill now names a command or behavior that older CLIs lack: raise the minimum in metadata.heptabase-cli-version-range in skills/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.
  6. Commit the bump (and any CLI-range edit). Preflight requires a clean tree, so do not run it against uncommitted manifest edits.
  7. Run preflight and fix any FAILs:
    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.
  8. 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.
  9. 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
  10. 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
  11. 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).

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.