Agent skill

Release Workflow

Release/publish the spikard Rust core crate and CLI end-to-end.

Install Release Workflow

skills CLI

$ npx skills add Goldziher/spikard --skill release-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Goldziher/spikard release-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Goldziher/spikard.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.ai-rulez/skills/release-workflow .claude/skills/release-workflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "release-workflow" agent skill from https://github.com/Goldziher/spikard/tree/main/.ai-rulez/skills/release-workflow into .claude/skills/release-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-workflow", 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.

$skill-installer

$skill-installer install https://github.com/Goldziher/spikard/tree/main/.ai-rulez/skills/release-workflow

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 Goldziher/spikard --skill release-workflow -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Goldziher/spikard release-workflow --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Goldziher/spikard.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.ai-rulez/skills/release-workflow .agents/skills/release-workflow && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "release-workflow" agent skill from https://github.com/Goldziher/spikard/tree/main/.ai-rulez/skills/release-workflow into .agents/skills/release-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-workflow", 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 Goldziher/spikard --skill release-workflow -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Goldziher/spikard release-workflow --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Goldziher/spikard.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.ai-rulez/skills/release-workflow .cursor/skills/release-workflow && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "release-workflow" agent skill from https://github.com/Goldziher/spikard/tree/main/.ai-rulez/skills/release-workflow into .cursor/skills/release-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-workflow", 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.

gemini skills install

$ gemini skills install https://github.com/Goldziher/spikard.git --path .ai-rulez/skills/release-workflow

--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 Goldziher/spikard --skill release-workflow -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Goldziher/spikard release-workflow --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Goldziher/spikard.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.ai-rulez/skills/release-workflow .gemini/skills/release-workflow && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "release-workflow" agent skill from https://github.com/Goldziher/spikard/tree/main/.ai-rulez/skills/release-workflow into .gemini/skills/release-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-workflow", 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.

GitHub CLI

$ gh skill install Goldziher/spikard release-workflow

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 Goldziher/spikard --skill release-workflow -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Goldziher/spikard.git skills-src && mkdir -p .github/skills && cp -r skills-src/.ai-rulez/skills/release-workflow .github/skills/release-workflow && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "release-workflow" agent skill from https://github.com/Goldziher/spikard/tree/main/.ai-rulez/skills/release-workflow into .github/skills/release-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-workflow", 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 Goldziher/spikard --skill release-workflow -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Goldziher/spikard release-workflow --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Goldziher/spikard.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.ai-rulez/skills/release-workflow .opencode/skills/release-workflow && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "release-workflow" agent skill from https://github.com/Goldziher/spikard/tree/main/.ai-rulez/skills/release-workflow into .opencode/skills/release-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-workflow", 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-workflow
GitHub stars: 123
Token cost: ~909 tokens
SKILL.md length: 344 words
Files: 1
Skills in repo: 2
Repo updated: Oct 3, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Release/publish the spikard Rust core crate and CLI end-to-end.

Works in 6 steps: Set the version → Update the CHANGELOG → Clean-tree precondition (hard gate) → …
Tasks that involve Changelog and release notes
SKILL.md covers 1. Set the version, 2. Update the CHANGELOG, 3. Clean-tree precondition… and 4. Commit, tag, and publish…, plus 3 more sections
Calls git, gh and cargo

What it does

Release Workflow is an agent skill from Goldziher/spikard. Release/publish the spikard Rust core crate and CLI end-to-end. Load when releasing or publishing spikard — cutting a new version, tagging, running gh release create, and installing the released build locally. Covers version set via Taskfile, CHANGELOG roll, the clean-tree precondition, GitHub release, local install, and artifact cleanup.

Its SKILL.md is about 910 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering Changelog and release notes, gRPC and Protobuf and Project scaffolding. It works with Rust, GitHub, Model Context Protocol and gRPC. The repository describes itself as: Codegen-first polyglot web toolkit: one Rust core, 14 language bindings, spec-driven codegen (OpenAPI, AsyncAPI, GraphQL, gRPC, SQL to HTTP) and a 13-tool MCP server… The licence is MIT.

When your agent uses it

Tasks that involve Changelog and release notes
Tasks that involve gRPC and Protobuf
Tasks that involve Project scaffolding

Example prompts

“/release-workflow”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

Set the version
Update the CHANGELOG
Clean-tree precondition (hard gate)
Commit, tag, and publish the GitHub release
Install the released CLI locally
Clean up build artifacts

What it can do on your machine

Read from SKILL.md and the folder at commit 083b29c. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- git
- gh
- cargo
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, 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 Workflow loads about 909 tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 344 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~90
When it runs · the whole SKILL.md, loaded when a task matches: ~909

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from Goldziher/spikard at commit 083b29c, republished under its MIT licence (© Goldziher). 344 words, ~909 tokens.

Download SKILL.mdSave it as .claude/skills/release-workflow/SKILL.md (or your agent's skills folder).

name: release-workflow
description: Release/publish the spikard Rust core crate and CLI end-to-end. Load when releasing or publishing spikard — cutting a new version, tagging, running `gh release create`, and installing the released build locally. Covers version set via Taskfile, CHANGELOG roll, the clean-tree precondition, GitHub release, local install, and artifact cleanup.

Spikard Release Workflow

Ground truth: spikard is a Rust workspace (core library + spikard-cli + polyglot bindings). It has no set-version task — the equivalent is task version:set (a version-sync include). Cargo.toml is the single source of truth; version:set syncs it to every binding manifest.

1. Set the version

bash

task version:set -- X.Y.Z        # e.g. task version:set -- 0.7.0-rc.1

version:set takes the version as a -- positional argument (CLI_ARGS). It runs alef sync-versions --set <version> then the full sync (regenerate READMEs, docs, bindings, scaffold, stubs, e2e, and precise cargo update for the core crate across dependent manifests). Bump variants also exist: task version:bump:patch, task version:bump:minor, task version:bump:major. task version:show prints the current version.

Verify:

bash

task version:show
grep -m1 '^version' Cargo.toml

2. Update the CHANGELOG

Move every [Unreleased] bullet in CHANGELOG.md into a new ## [X.Y.Z] - YYYY-MM-DD section (grouped Added / Changed / Fixed / Removed). Re-create an empty [Unreleased]. Never tag an empty section.

3. Clean-tree precondition (hard gate)

Never release a dirty or failing tree.

bash

poly fmt --check .    # formatting clean (task format:check)
poly lint .           # lint clean (task lint)
task test             # Rust core tests pass (rust:test)

Use poly fmt --fix . (or task format) to apply formatting, then re-stage. For a full cross-binding gate before a release, run task test:all (task test + alef test). Optionally validate manifests with task publish:validate (alef publish validate). Fix any failure — do not release past it.

4. Commit, tag, and publish the GitHub release

bash

git add -A
git commit -m "chore(release): X.Y.Z"
git tag -a vX.Y.Z -m "vX.Y.Z"
git push origin main
git push origin vX.Y.Z
gh release create vX.Y.Z --title "vX.Y.Z" --generate-notes

Add --prerelease for RC/beta tags. Use --notes-file from the new CHANGELOG section instead of --generate-notes when the changelog entry is richer. A bare git tag is not a release — always run gh release create. Tag-based releases trigger the multi-platform / multi-registry publish workflows.

5. Install the released CLI locally

bash

cargo install --path crates/spikard-cli --force

Installs the spikard CLI binary from the workspace. (If a change is only in the core crate, task build:release builds spikard core; task build:cli builds the CLI binary to target/release/spikard.) Confirm which spikard and spikard --version reflect X.Y.Z.

6. Clean up build artifacts

bash

task clean        # cargo clean + alef clean + rm -rf dist/ .alef/ caches

task clean runs cargo clean (removing target/ to reclaim space) plus alef clean and removes dist/, .alef/, and language caches.

Anti-patterns

Reaching for a set-version task — spikard uses task version:set -- X.Y.Z.
Hand-editing version in Cargo.toml or any binding manifest instead of task version:set.
Releasing a dirty or lint/test-failing tree.
Tagging without gh release create.
AI attribution in commit/tag/release text.

Files

Just SKILL.md in .ai-rulez/skills/release-workflow of Goldziher/spikard.

Open the folder on GitHubat commit 083b29c

Compare with similar skills

Release Workflow 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.

Release Workflow compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Release Workflow this skillGoldziher/spikard	123	—	~909	Automated safety check: Pass	MIT	5 days ago
Dev Rulesrust-dd/tako	162	—	~810	Automated safety check: Pass	MIT	7 days ago
Docs Writingrust-dd/tako	162	—	~2.8k	Automated safety check: Pass	MIT	7 days ago
Uxcholon-run/uxc	116	—	~1.8k	Automated safety check: Pass	MIT	23 days ago
Use Yaakmountain-loop/yaak	19k	—	~1.9k	Automated safety check: Pass	MIT	yesterday
Plugin Release CheckVoidenHQ/voiden	1.9k	—	~857	Automated safety check: Pass	Apache-2.0	yesterday

Similar skills

Dev Rules
rust-dd/tako
General coding-style rules to apply to every project. An agent skill from rust-dd/tako.
162 GitHub stars~810 tokensUpdated 7 days ago
Backend & APIsAuto-check passed
Docs Writing
rust-dd/tako
Conventions for writing and maintaining tako documentation pages under website/content/docs/.
162 GitHub stars~2.8k tokensUpdated 7 days ago
Backend & APIsAuto-check passed
Uxc
holon-run/uxc
Discover and call remote schema-exposed interfaces with UXC.
116 GitHub stars~1.8k tokensUpdated 23 days ago
Backend & APIsAuto-check passed
Use Yaak
mountain-loop/yaak
A skill your agent uses when the user mentions Yaak, a Yaak workspace, or the yaak command, or asks to call, hit, or smoke test HTTP/REST endpoints, save or organize API requests for reuse or manual…
19k GitHub stars~1.9k tokensUpdated yesterday
Backend & APIsAuto-check passed
Plugin Release Check
VoidenHQ/voiden
A skill your agent uses whenever a plugin under plugins/<name is updated/pushed, or whenever asked to write a changelog/release for the app or a plugin.
1.9k GitHub stars~857 tokensUpdated yesterday
Backend & APIsAuto-check passed
Spider King
aoyunyang/spider-king-skill
Pure-web protocol reverse skill: turn hostile browser clients into browser-free Python collectors.
507 GitHub stars~7.3k tokensUpdated 1 mo ago
Backend & APIsAuto-check passed

Questions about Release Workflow

What does Release Workflow do?

Release/publish the spikard Rust core crate and CLI end-to-end. Release Workflow is an agent skill from Goldziher/spikard. Release/publish the spikard Rust core crate and CLI end-to-end.

When should I use Release Workflow?

Release Workflow fits situations like: tasks that involve Changelog and release notes; tasks that involve gRPC and Protobuf; tasks that involve Project scaffolding.

How do I install Release Workflow in Claude Code?

Run `npx skills add Goldziher/spikard --skill release-workflow -a claude-code`. Or copy the skill folder (.ai-rulez/skills/release-workflow in Goldziher/spikard) into .claude/skills/release-workflow in your project. Claude Code loads it when a task matches its description.

How do I install Release Workflow in Codex?

Run `npx skills add Goldziher/spikard --skill release-workflow -a codex`. Or copy the skill folder (.ai-rulez/skills/release-workflow in Goldziher/spikard) into .agents/skills/release-workflow in your project. Codex loads it when a task matches its description.

Can I use Release Workflow 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 Goldziher/spikard --skill release-workflow -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-workflow, .gemini/skills/release-workflow, .github/skills/release-workflow and .opencode/skills/release-workflow in your project.

What does Release Workflow need to run?

Going by SKILL.md and its folder, Release Workflow needs the command-line tools its instructions call (git, gh and cargo).

Does Release Workflow access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Release Workflow 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. Review the folder before installing.

What licence does Release Workflow use?

Release Workflow 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 Workflow use?

About 909 tokens (SKILL.md is roughly 3.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 Workflow?

Skills that share tags, products or a category with Release Workflow: Dev Rules (rust-dd/tako, 162 stars), Docs Writing (rust-dd/tako, 162 stars), Uxc (holon-run/uxc, 116 stars) and Use Yaak (mountain-loop/yaak, 19k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Workflow?

Goldziher (a GitHub user) maintains it in Goldziher/spikard, which has 123 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 3, 2026.

Source: Goldziher/spikard on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Release Workflow

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Spikard Release Workflow

1. Set the version

2. Update the CHANGELOG

3. Clean-tree precondition (hard gate)

4. Commit, tag, and publish the GitHub release

5. Install the released CLI locally

6. Clean up build artifacts

Anti-patterns

Files

Compare with similar skills

Similar skills

Dev Rules

Docs Writing

Uxc

Use Yaak

Plugin Release Check

Spider King

More from Goldziher/spikard

Spikard

Related

Questions about Release Workflow