agentleFS
Sign inStart free
jame581jame581/LogseqBrain/.claude/skills/release/SKILL.md

release

Skill18 starsChanged 24 days agoMITView on GitHub

Cut a logseq-brain release — eval gate, version bump in plugin.json and BRAIN_VERSION, tag, GitHub release, .plugin rebuild, skillsmith marketplace bump. Invoke only when the user asks to release.

  • Commits and pushes

196 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, 0 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 186 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Commit with chore(release): prepare vX.Y.Z, then tag it annotated and push the tag.

    line 27
  2. Very specific:

    Create the GitHub release (gh release create vX.Y.Z --notes-file …).

    line 28
  3. Very specific:

    Update the logseq-brain project page in the brain with the release (/brain-save).

    line 34

“Common” is measured: kept by at least 6 in 10 of the 186 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

Release logseq-brain

CONTRIBUTING.md § Releasing a new version is the source of truth. Read it now, in full, and follow it step by step. This skill only adds the order of operations and the checks that have slipped before.

Argument: the version X.Y.Z. If none was given, read plugin/.claude-plugin/plugin.json and ROADMAP.md and ask which version to cut.

Before step 0

  • The version branch vX.Y.Z is merged to main by PR, and the local main is pulled. Releases are cut from main.
  • git status is clean.

Gates — stop and report on any failure

  1. The tests workflow is green on the release commit: gh run list --branch main --limit 3.
  2. The eval suite passes on the release commit. It runs only as the logseq-eval WSL user and draws on plan usage, so ask before launching it. Use the /eval skill. Record the load-digest and save-basic tool-call figures for the release notes.

Mechanical steps

  • Bump both plugin/.claude-plugin/plugin.json "version" and BRAIN_VERSION in plugin/skills/_shared/bin/brain. The version-matches-plugin golden case fails until they agree, so run sh tests/run.sh 'version-*'.
  • Annotate the version's design spec with the release measurement if the spec calls for it. Never rewrite the spec body.
  • Commit with chore(release): prepare vX.Y.Z, then tag it annotated and push the tag. Confirm with the user before pushing.
  • Create the GitHub release (gh release create vX.Y.Z --notes-file …). Draft the notes from the commits since the previous tag, and include the eval figures.

After the tag — the steps that get forgotten

  • Rebuild the Cowork archive from the tag and verify the listing: it must contain skills/_shared/bin/brain and skills/_shared/lib/core.awk, and must not contain tests/ or tools/.
  • Bump .claude-plugin/marketplace.json in the sibling ../skillsmith repo. First run git -C ../skillsmith pull, and never assert its state from memory. That repo has its own commit and push. Confirm before pushing.
  • Update the logseq-brain project page in the brain with the release (/brain-save).

End with a checklist that shows each step as done, skipped (and why), or blocked.

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.

Check your setup, free