Cut Release

OrganizationPopular

spiculedata

cut-release

Cut a Saiku release via Gitflow — version bump, release branch, PR to main, tag, back-merge, and post-release chores. Use when asked to release, tag, or publish a new Saiku version.

Overview

Publisher	spiculedata
Repository	`saiku`
Skill name	`cut-release`
Stars	1.3K
Forks	658
Bundled files	Instructions only
License	Apache-2.0
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by spiculedata on GitHub. Read the source before you install it.

Installation

Install the Cut Release AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/spiculedata/saiku/tree/development/.agents/skills/cut-release
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/spiculedata/saiku.git /tmp/saiku
mkdir -p .claude/skills
cp -r /tmp/saiku/.agents/skills/cut-release .claude/skills/cut-release

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Cut Release in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Cut Release on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Cut Release is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Cut a release

Publishing is entirely CI-driven. Pushing a v* tag runs release.yml, which publishes the fat-JAR and dist zip (GitHub release assets), module jars (GitHub Packages), the Docker image (ghcr.io/spiculedata/saiku:<version>) and the npm embed package. Never mvn deploy locally.

Bump the version on a branch off development. Every reactor pom carries the literal release version (non-SNAPSHOT).
```
bash
mvn versions:set -DnewVersion=X.Y.Z -DgenerateBackupPoms=false
```
versions:set misses saiku-bom/pom.xml, so fix that by hand. Check with git grep -n '<version>OLD' -- '*pom.xml'.
Update CHANGELOG.md with a section for the release, and fold in any docs/release-notes-*-draft.md. Merge this to development via PR.
Cut release/X.Y.Z off development and push it. release-prep.yml runs the mvn verify gate.
Open a PR from release/X.Y.Z to main and merge it once green.

gh pr merge can silently no-op while a required check is pending. Before tagging, confirm main actually advanced: git fetch && git log -1 origin/main should show the release merge and the new version.
Tag the merged main HEAD and push the tag.
```
bash
git tag vX.Y.Z origin/main && git push origin vX.Y.Z
```
If you tagged the wrong commit: gh run cancel the release run, git push origin :refs/tags/vX.Y.Z, git tag -d vX.Y.Z, then re-tag correctly.
Replace the auto-generated release notes (a raw commit list) with the changelog section: gh release edit vX.Y.Z --notes-file <file>.
Back-merge main into development via a chore/back-merge-X.Y.Z PR.
Post-release: bump LATEST_VERSION in telemetry/wrangler.toml (PR to development), and redeploy the demo box.

Frequently asked questions

What does the Cut Release AI skill do?

Cut a Saiku release via Gitflow — version bump, release branch, PR to main, tag, back-merge, and post-release chores. Use when asked to release, tag, or publish a new Saiku version.

Why use Cut Release on TypingMind?

Because you install it once and use it with any model. Cut Release is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Cut Release in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/spiculedata/saiku/tree/development/.agents/skills/cut-release. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Cut Release?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Cut Release?

As many as you like. As long as a model supports skills, you can use Cut Release with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Cut Release AI skill free?

Yes. It is published on GitHub by spiculedata under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Openclaw Repair Sweep

openclaw

OrganizationPopular

Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.

Openclaw Test Performance

openclaw

OrganizationPopular

Benchmark, diagnose, and optimize OpenClaw test and plugin-suite runtime, import hotspots, CPU/RSS, heap growth, and slow coverage paths.

Openclaw Testing

Choose proportional OpenClaw tests and checks, diagnose failures, and route environment-sensitive or release proof to its owner.

Release Openclaw Ci

Run, watch, debug, and summarize OpenClaw full release CI, release checks, live provider gates, install/update proofs, and release-secret preflights.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Cut a release

Frequently asked questions

Related AI Skills

Set up your own AI workspace now