cut-release SKILL.md skillA
cut-release from spiculedata/saiku is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add spiculedata/saiku/cut-release@git:20261011.8c1f45fPins git:20261011.8c1f45f in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- spiculedata/saiku
- Path
.agents/skills/cut-release/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261011.8c1f45f, committed Oct 11, 2026
- Size
- 2,009 bytes
- Repository stars
- 1,333
- License
- Apache-2.0
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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. 1. **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'`. 2. **Update `CHANGELOG.md`** with a section for the release, and fold in any `docs/release-notes-*-draft.md`. Merge this to `development` via PR. 3. **Cut `release/X.Y.Z` off `development` and push it.** `release-prep.yml` runs the `mvn verify` gate. 4. **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. …
Read the whole file at its exact version.
How to install
mdr add spiculedata/saiku/cut-release@sha256:1adece660e7c1087The line at the top of this page pins the label git:20261011.8c1f45f, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_eg633yt4z72umolv)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 11, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2009 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
spiculedata/saiku · 1,333 stars · license Apache-2.0 · pushed 2026-10-18 · branch development
API
GET https://markdownregistry.com/api/v1/artifacts/art_eg633yt4z72umolv GET https://markdownregistry.com/api/v1/resolve?ref=spiculedata/saiku/cut-release GET https://markdownregistry.com/api/v1/blob/1adece660e7c1087a2105b08ecbb7d27d58d9122b3e8e26ff3b0e5ba8385e77c
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from spiculedata/saiku
Every file in spiculedata/saiku