Agent skill

Release

Create a new release with tag, GitHub release, and homebrew-tap update

MITAuto-check passedDevelopment

Install Release

skills CLI

$ npx skills add trasta298/keifu --skill release -a claude-code

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

GitHub CLI

$ gh skill install trasta298/keifu release --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/trasta298/keifu.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release .claude/skills/release && 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" agent skill from https://github.com/trasta298/keifu/tree/main/.agents/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.

$skill-installer

$skill-installer install https://github.com/trasta298/keifu/tree/main/.agents/skills/release

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 trasta298/keifu --skill release -a codex

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

GitHub CLI

$ gh skill install trasta298/keifu release --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/trasta298/keifu.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/release .agents/skills/release && 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" agent skill from https://github.com/trasta298/keifu/tree/main/.agents/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 trasta298/keifu --skill release -a cursor

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

GitHub CLI

$ gh skill install trasta298/keifu release --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/trasta298/keifu.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/release .cursor/skills/release && 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" agent skill from https://github.com/trasta298/keifu/tree/main/.agents/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.

gemini skills install

$ gemini skills install https://github.com/trasta298/keifu.git --path .agents/skills/release

--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 trasta298/keifu --skill release -a gemini-cli

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

GitHub CLI

$ gh skill install trasta298/keifu release --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/trasta298/keifu.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/release .gemini/skills/release && 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" agent skill from https://github.com/trasta298/keifu/tree/main/.agents/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 trasta298/keifu 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 trasta298/keifu --skill release -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/trasta298/keifu.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/release .github/skills/release && 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" agent skill from https://github.com/trasta298/keifu/tree/main/.agents/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 trasta298/keifu --skill release -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 trasta298/keifu release --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/trasta298/keifu.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/release .opencode/skills/release && 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" agent skill from https://github.com/trasta298/keifu/tree/main/.agents/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: 811
Token cost: ~1.2k tokens
SKILL.md length: 401 words
Files: 1
Skills in repo: 2
Repo updated: Jul 30, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Create a new release with tag, GitHub release, and homebrew-tap update

Works in 6 steps: Analyze Changes and Determine… → Ask User for Version Bump Type → Update Version and Create Release → …
Development work in your project
SKILL.md covers Instructions and Error Handling
Calls git, gh and cargo

What it does

Release is an agent skill from trasta298/keifu. Create a new release with tag, GitHub release, and homebrew-tap update

Its SKILL.md is about 1.2k 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. It works with Homebrew, GitHub, Rust and Git. The repository describes itself as: Git genealogy, untangled. A TUI for navigating commit graphs with color and clarity. The licence is MIT.

When your agent uses it

Development work in your project

Example prompts

“/release”

Workflow steps

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

Analyze Changes and Determine Recommended Version
Ask User for Version Bump Type
Update Version and Create Release
Wait for GitHub Actions Release Workflow
Update Homebrew Tap
Report Success

What it can do on your machine

Read from SKILL.md and the folder at commit 4d9f033. 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
- curl
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, gh and curl, 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 1.2k tokens when it runs. Until then it costs about 20 tokens; SKILL.md has 401 words of instructions outside code blocks.

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

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 trasta298/keifu at commit 4d9f033, republished under its MIT licence (© trasta298). 401 words, ~1,183 tokens.

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

name: release
description: Create a new release with tag, GitHub release, and homebrew-tap update

Release Skill

This skill creates a new release by:

Bumping the version in Cargo.toml
Creating a git commit and tag
Pushing to trigger GitHub Actions release workflow
Waiting for the release to complete
Updating the homebrew-tap formula

Instructions

Step 1: Analyze Changes and Determine Recommended Version

First, get the current version from Cargo.toml and analyze changes since the last release:

bash

# Get current version
grep '^version' Cargo.toml | head -1 | sed 's/.*"\(.*\)".*/\1/'

# Get the latest tag
git describe --tags --abbrev=0 2>/dev/null || echo "No tags found"

# Get commits since last tag (or all commits if no tag)
LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null)
if [ -n "$LAST_TAG" ]; then
  git log --oneline "$LAST_TAG"..HEAD
else
  git log --oneline
fi

Determine the recommended version bump based on conventional commits:

major: Breaking changes (commits with BREAKING CHANGE or !: in message)
minor: New features (commits starting with feat: or similar)
patch: Bug fixes, documentation, refactoring, etc. (commits starting with fix:, docs:, refactor:, chore:, etc.)

Step 2: Ask User for Version Bump Type

Use the AskUserQuestion tool to ask the user which version bump to apply. Put the recommended option first based on the analysis above.

Question format:

Header: "Version"
Question: "Which version bump do you want to apply? Current version: X.Y.Z"
Options should be ordered with recommended first, e.g., if patch is recommended:
1. "patch (Recommended)" -> "X.Y.Z+1 - Bug fixes and minor changes"
2. "minor" -> "X.Y+1.0 - New features"
3. "major" -> "X+1.0.0 - Breaking changes"

Step 3: Update Version and Create Release

After user confirms the version bump:

Update Cargo.toml version:
- Calculate the new version based on user selection
- Edit the version line in Cargo.toml
Update Cargo.lock:
bash
```
cargo update -p keifu
```

Commit the version bump:

bash

git add Cargo.toml Cargo.lock
git commit -m "$(cat <<'EOF'
Bump version to NEW_VERSION

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
EOF
)"

Create and push the tag:

bash

git tag vNEW_VERSION
git push origin main --tags

Step 4: Wait for GitHub Actions Release Workflow

The release workflow is triggered by the tag push. Wait for it to complete:

bash

# Wait for the workflow to start and complete
gh run list --workflow=release.yaml --limit=1 --json databaseId,status,conclusion

# Watch the workflow progress
gh run watch $(gh run list --workflow=release.yaml --limit=1 --json databaseId --jq '.[0].databaseId')

If the workflow fails, inform the user and stop. Do not proceed with homebrew-tap update.

Show full SKILL.md (211 more words)Show less

Step 5: Update Homebrew Tap

After the release workflow completes successfully:

Create a temporary directory and clone homebrew-tap:

bash

TEMP_DIR=$(mktemp -d)
git clone git@github.com:trasta298/homebrew-tap.git "$TEMP_DIR"

Download release assets and calculate SHA256:

bash

NEW_VERSION="X.Y.Z"  # The new version without 'v' prefix
TAG="vX.Y.Z"  # The tag with 'v' prefix

# Get SHA256 for each platform
TARGETS=(
  "aarch64-apple-darwin"
  "x86_64-apple-darwin"
  "aarch64-unknown-linux-gnu"
  "x86_64-unknown-linux-gnu"
)

for TARGET in "${TARGETS[@]}"; do
  URL="https://github.com/trasta298/keifu/releases/download/$TAG/keifu-$TAG-$TARGET.tar.gz"
  SHA=$(curl -sL "$URL" | sha256sum | cut -d' ' -f1)
  echo "$TARGET: $SHA"
done

Update the formula file ($TEMP_DIR/Formula/keifu.rb):
- Update the version line
- Update all URLs to use the new tag
- Update all sha256 values with the calculated hashes

Commit and push the changes:

bash

cd "$TEMP_DIR"
git add Formula/keifu.rb
git commit -m "$(cat <<'EOF'
Update keifu to NEW_VERSION

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
EOF
)"
git push origin main

Clean up the temporary directory:
bash
```
rm -rf "$TEMP_DIR"
```

Step 6: Report Success

Inform the user that the release is complete with:

The new version number
Link to the GitHub release
Confirmation that homebrew-tap was updated

Error Handling

If there are uncommitted changes, warn the user and ask if they want to proceed
If the GitHub Actions workflow fails, stop and report the error
If homebrew-tap update fails, report the error but note that the main release was successful

Files

Just SKILL.md in .agents/skills/release of trasta298/keifu.

Open the folder on GitHubat commit 4d9f033

Compare with similar skills

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.

Release compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Release this skilltrasta298/keifu	811	—	~1.2k	Automated safety check: Pass	MIT	2 mo ago
Worktrunk Release Workflowmax-sixty/worktrunk	9k	—	~6.9k	Automated safety check: Pass	Custom licence	today
AnyDrag Release RoutineXueshiQiao/AnyDrag	227	—	~2.6k	Automated safety check: Pass	GPL-3.0	4 days ago
Kt Search Releasejillesvangurp/kt-search	155	—	~1.2k	Automated safety check: Pass	MIT	3 mo ago
Firewood Reviewava-labs/firewood	153	—	~2.1k	Automated safety check: Notes	Custom licence	today
Release VersionGOODBOY008/r-shell	151	—	~4k	Automated safety check: Pass	MIT	yesterday

Similar skills

Worktrunk Release Workflow
max-sixty/worktrunk
Walks a maintainer through cutting a Worktrunk release: sync the release branch, pass two test gates, review the changes, then publish.
9k GitHub stars~6.9k tokensUpdated today
DevelopmentAuto-check passed
AnyDrag Release Routine
XueshiQiao/AnyDrag
Runs the full AnyDrag release process end to end, from cumulative bilingual release notes through version bumping to watching CI and the Homebrew cask update.
227 GitHub stars~2.6k tokensUpdated 4 days ago
DevelopmentAuto-check passed
Kt Search Release
jillesvangurp/kt-search
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…
155 GitHub stars~1.2k tokensUpdated 3 mo ago
DevelopmentAuto-check passed
Firewood Review
ava-labs/firewood
A skill your agent uses when reviewing ava-labs/firewood code changes — pull request or local workspace.
153 GitHub stars~2.1k tokensUpdated today
DevelopmentAuto-check: notes
Release Version
GOODBOY008/r-shell
Release a new r-shell version and create a published GitHub release with contributor credits.
151 GitHub stars~4k tokensUpdated yesterday
DevelopmentAuto-check passed
Kanvibe Release Deploy
rookedsysc/kanvibe
A skill your agent uses whenever releasing or deploying KanVibe desktop from a clean, up-to-date dev checkout: ask only for the target version and release-note approval, then let the AI update…
143 GitHub stars~12k tokensUpdated today
DevelopmentAuto-check: notes

Questions about Release

What does Release do?

Create a new release with tag, GitHub release, and homebrew-tap update. Release is an agent skill from trasta298/keifu.

When should I use Release?

Release fits situations like: development work in your project.

How do I install Release in Claude Code?

Run `npx skills add trasta298/keifu --skill release -a claude-code`. Or copy the skill folder (.agents/skills/release in trasta298/keifu) 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 trasta298/keifu --skill release -a codex`. Or copy the skill folder (.agents/skills/release in trasta298/keifu) 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 trasta298/keifu --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, gh, cargo and curl).

Does Release access the network?

SKILL.md contains no URLs. Its commands use git, gh and curl, 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 MIT 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 1.2k tokens (SKILL.md is roughly 4.7k 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: Worktrunk Release Workflow (max-sixty/worktrunk, 9k stars), AnyDrag Release Routine (XueshiQiao/AnyDrag, 227 stars), Kt Search Release (jillesvangurp/kt-search, 155 stars) and Firewood Review (ava-labs/firewood, 153 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release?

trasta298 (a GitHub user) maintains it in trasta298/keifu, which has 811 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on July 30, 2026.

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

Release

Install Release

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

Release Skill

Instructions

Step 1: Analyze Changes and Determine Recommended Version

Step 2: Ask User for Version Bump Type

Step 3: Update Version and Create Release

Step 4: Wait for GitHub Actions Release Workflow

Step 5: Update Homebrew Tap

Step 6: Report Success

Error Handling

Files

Compare with similar skills

Similar skills

Worktrunk Release Workflow

AnyDrag Release Routine

Kt Search Release

Firewood Review

Release Version

Kanvibe Release Deploy

More from trasta298/keifu

Debug Tui

Questions about Release

Install Release

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

Release Skill

Instructions

Step 1: Analyze Changes and Determine Recommended Version

Step 2: Ask User for Version Bump Type

Step 3: Update Version and Create Release

Step 4: Wait for GitHub Actions Release Workflow

Step 5: Update Homebrew Tap

Step 6: Report Success

Error Handling

Files

Compare with similar skills

Similar skills

Worktrunk Release Workflow

AnyDrag Release Routine

Kt Search Release

Firewood Review

Release Version

Kanvibe Release Deploy

More from trasta298/keifu

Debug Tui

Related

Questions about Release