Install the "release" agent skill from https://github.com/sol4k/sol4k/tree/main/.claude/skills/release into .claude/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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.
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 sol4k/sol4k --skill release -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "release" agent skill from https://github.com/sol4k/sol4k/tree/main/.claude/skills/release into .agents/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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 sol4k/sol4k --skill release -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "release" agent skill from https://github.com/sol4k/sol4k/tree/main/.claude/skills/release into .cursor/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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.
--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 sol4k/sol4k --skill release -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "release" agent skill from https://github.com/sol4k/sol4k/tree/main/.claude/skills/release into .gemini/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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 sol4k/sol4k release
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 sol4k/sol4k --skill release -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "release" agent skill from https://github.com/sol4k/sol4k/tree/main/.claude/skills/release into .github/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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 sol4k/sol4k --skill release -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "release" agent skill from https://github.com/sol4k/sol4k/tree/main/.claude/skills/release into .opencode/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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
GitHub stars
135
Token cost
~949 tokens
SKILL.md length
429 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
Apache-2.0
At a glance
Bump the sol4k library version everywhere, open a release PR, and draft GitHub release notes.
Works in 5 steps: gradle.properties — the currentVersion=… → docs/README.md — the Gradle… → docs/README_JP.md — same two lines. → …
The user wants to release/cut a new version (e.g
SKILL.md covers Inputs, Files to update, Release notes and Steps
Calls git and gh
What it does
Release is an agent skill from sol4k/sol4k. Bump the sol4k library version everywhere, open a release PR, and draft GitHub release notes. Use when the user wants to release/cut a new version (e.g. "release 0.8.0", "bump version to X"). Updates gradle.properties and all docs/README.md dependency snippets, creates a branch and PR, and drafts release notes from the commits since the last version.
Its SKILL.md is about 950 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 Development, covering Changelog and release notes, Android development and Technical documentation. It works with Gradle, GitHub, Kotlin and Java. The repository describes itself as: Kotlin, Java, and Android client for Solana ⛓️. The licence is Apache-2.0.
When your agent uses it
The user wants to release/cut a new version (e.g
Tasks that involve Changelog and release notes
Tasks that involve Android development
Example prompts
“release 0.8.0”
“bump version to X”
“/release”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
1gradle.properties — the currentVersion= property.
2docs/README.md — the Gradle implementation 'org.sol4k:sol4k:X' line and
3docs/README_JP.md — same two lines.
4docs/README_KR.md — same two lines.
5docs/README_ZH.md — same two lines.
What it can do on your machine
Read from SKILL.md and the folder at commit a166edd. 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
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 loads about 949 tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 429 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
~949
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.
Download SKILL.mdSave it as .claude/skills/release/SKILL.md (or your agent's skills folder).
name
release
description
Bump the sol4k library version everywhere, open a release PR, and draft GitHub release notes. Use when the user wants to release/cut a new version (e.g. "release 0.8.0", "bump version to X"). Updates gradle.properties and all docs/README*.md dependency snippets, creates a branch and PR, and drafts release notes from the commits since the last version.
Release a new sol4k version
Bumps the project version across every file that hardcodes it and opens a
release PR, mirroring past release PRs (e.g. #184, #202).
Inputs
New version (required), e.g. 0.8.0. Ask the user if not provided.
Determine the current version from gradle.properties
(currentVersion=...).
Files to update
The version string appears in exactly these files — replace the current
version with the new one in each:
gradle.properties — the currentVersion= property.
docs/README.md — the Gradle implementation 'org.sol4k:sol4k:X' line and
the Maven <version>X</version> line.
docs/README_JP.md — same two lines.
docs/README_KR.md — same two lines.
docs/README_ZH.md — same two lines.
Do not touch test data, changelogs, or any other 0.x.y occurrences — only the
five files above carry the published version.
Release notes
After the PR is opened, draft the GitHub release notes so the user can copy them
when publishing the release (the release is created manually on GitHub, not by
this skill). Releases are GitHub Releases whose tag is the bare version (e.g.
0.8.0) with a title of <version> - <short summary> and a body of bullet
points — match the style of past releases (gh release view 0.8.0).
Build the notes from the commits between the previous version tag and the tip of
main (exclude the version-bump commit itself):
shell
git log <old-version>..origin/main --oneline
Turn each meaningful commit into a bullet, dropping the (#NNN) PR suffix and
rewording terse commit subjects into user-facing changes. Pick a concise title
summary from the most significant change (e.g. a Kotlin bump, a new API).
Present the result as a ready-to-copy block, e.g.:
Title: 0.8.1 - Configurable RPC transport
- Make the RPC transport configurable and add support for custom headers
Show full SKILL.md (196 more words)Show less
Steps
Read the current version from gradle.properties.
Create a branch named <new-version>-release (e.g. 0.8.0-release). If the
user is already on such a branch and just wants the edits committed there,
skip branch creation.
Replace the old version with the new one in the five files above. A quick way:shell
Verify with git diff that exactly 9 lines changed (1 in gradle.properties,
2 in each of the 4 READMEs).
Commit:
Update version to <new-version>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Push the branch and open a PR with gh pr create:
Title: <new-version> release
Body (matching prior release PRs):
Version bump from <old> to <new> across all configuration and documentation files.
**Changes:**
- `gradle.properties`: Updated `currentVersion` property
- `docs/README*.md`: Updated version strings in Gradle and Maven dependency examples (English, Japanese, Korean, Chinese variants)
End the body with the standard Claude Code attribution line.
Draft the GitHub release notes (see Release notes above) from
git log <old-version>..origin/main --oneline, and present them to the user
as a ready-to-copy title + body block for when they publish the release.
Release 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.
A skill your agent uses when the user wants to cut, publish, tag, or create a GitHub release for kt-search, especially when the task includes version bumping, validating that commits are pushed…
A skill your agent uses when reviewing the Harmonica restart plan against reality — after a phase PR or milestone merges, before proposing the next phase, or when asked "are the specs up to date" /…
Bump the sol4k library version everywhere, open a release PR, and draft GitHub release notes. Release is an agent skill from sol4k/sol4k. Bump the sol4k library version everywhere, open a release PR, and draft GitHub release notes.
When should I use Release?
Release fits situations like: the user wants to release/cut a new version (e.g; tasks that involve Changelog and release notes; tasks that involve Android development.
How do I install Release in Claude Code?
Run `npx skills add sol4k/sol4k --skill release -a claude-code`. Or copy the skill folder (.claude/skills/release in sol4k/sol4k) into .claude/skills/release in your project. Claude Code loads it when a task matches its description.
How do I install Release in Codex?
Run `npx skills add sol4k/sol4k --skill release -a codex`. Or copy the skill folder (.claude/skills/release in sol4k/sol4k) into .agents/skills/release in your project. Codex loads it when a task matches its description.
Can I use Release 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 sol4k/sol4k --skill release -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, .gemini/skills/release, .github/skills/release and .opencode/skills/release in your project.
What does Release need to run?
Going by SKILL.md and its folder, Release needs the command-line tools its instructions call (git and gh).
Does Release 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 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 use?
Release is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Release use?
About 949 tokens (SKILL.md is roughly 3.8k 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?
Skills that share tags, products or a category with Release: Release Changelog (sk2andy/candy-browser, 485 stars), Kt Search Release (jillesvangurp/kt-search, 155 stars), Publish Release (Ayuilos/Miffan, 182 stars) and Plan Review (KenjiOhtsuka/harmonica, 131 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release?
sol4k (a GitHub organization) maintains it in sol4k/sol4k, which has 135 GitHub stars. The repository was last updated on September 28, 2026.
Source: sol4k/sol4k on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
