Agent skill

Release

Guides through the full gem release process — bump version, update CHANGELOG, tag, push to RubyGems, and create GitHub Release.

MITAuto-check: notesDevelopment

Install Release

skills CLI

$ npx skills add bibendi/schked --skill release -a claude-code

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

GitHub CLI

$ gh skill install bibendi/schked 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/bibendi/schked.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/bibendi/schked/tree/master/.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/bibendi/schked/tree/master/.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 bibendi/schked --skill release -a codex

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

GitHub CLI

$ gh skill install bibendi/schked 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/bibendi/schked.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/bibendi/schked/tree/master/.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 bibendi/schked --skill release -a cursor

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

GitHub CLI

$ gh skill install bibendi/schked 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/bibendi/schked.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/bibendi/schked/tree/master/.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/bibendi/schked.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 bibendi/schked --skill release -a gemini-cli

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

GitHub CLI

$ gh skill install bibendi/schked 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/bibendi/schked.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/bibendi/schked/tree/master/.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 bibendi/schked 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 bibendi/schked --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/bibendi/schked.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/bibendi/schked/tree/master/.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 bibendi/schked --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 bibendi/schked 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/bibendi/schked.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/bibendi/schked/tree/master/.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: 138
Token cost: ~670 tokens
SKILL.md length: 281 words
Files: 1
Skills in repo: 2
Repo updated: Aug 30, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Guides through the full gem release process — bump version, update CHANGELOG, tag, push to RubyGems, and create GitHub Release.

Works in 7 steps: Determine new version → Update version file → Update CHANGELOG → …
User asks to release a new version
SKILL.md covers Overview, Prerequisites, Step-by-step and Troubleshooting
Calls git and bundle; reaches rubygems.org

What it does

Release is an agent skill from bibendi/schked. Guides through the full gem release process — bump version, update CHANGELOG, tag, push to RubyGems, and create GitHub Release. Use when user asks to release a new version, cut a release, or similar.

Its SKILL.md is about 670 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 Deployment and Changelog and release notes. It works with Ruby, GitHub and Git. The repository describes itself as: Framework agnostic scheduler to run recurring jobs. The licence is MIT.

When your agent uses it

User asks to release a new version
Tasks that involve Deployment
Tasks that involve Changelog and release notes

Example prompts

“Use the release skill to guide through the full gem release process — bump version, update CHANGELOG, tag, push to RubyGems, and create GitHub Release”
“/release”

Requirements

Pre-approved tools (allowed-tools): Bash

Workflow steps

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

Determine new version
Update version file
Update CHANGELOG
Commit
Push to master
Tag and push the tag
CI does the rest

What it can do on your machine

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

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Bash
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- git
- bundle
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- rubygems.org
Also links to:
- semver.org
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 670 tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 281 words of instructions outside code blocks.

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

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
```
allowed-tools: Bash
```

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 bibendi/schked at commit c1f45ac, republished under its MIT licence (© bibendi). 281 words, ~670 tokens.

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

name: release
description: Guides through the full gem release process — bump version, update CHANGELOG, tag, push to RubyGems, and create GitHub Release. Use when user asks to release a new version, cut a release, or similar.
allowed-tools: Bash

Gem Release Process

Overview

The release process for the schked gem involves:

Bump version in lib/schked/version.rb
Add new section in CHANGELOG.md
Commit and push changes to master
Create and push a git tag vX.Y.Z
CI handles the rest (push to RubyGems via Trusted Publishing + GitHub Release)

Prerequisites

Trusted Publisher must be configured on RubyGems.org:
- Go to https://rubygems.org/gems/schked/settings
- Add a Trusted Publisher for:
  - Repository: bibendi/schked
  - Workflow: release.yml
  - Environment: (leave empty)
You must have push access to the repository
The CI must be green on master before releasing (recommended)

Step-by-step

1. Determine new version

Look at current version in lib/schked/version.rb. Follow SemVer.

2. Update version file

Edit lib/schked/version.rb and update the VERSION constant:

ruby

module Schked
  VERSION = "X.Y.Z"
end

3. Update CHANGELOG

Edit CHANGELOG.md and add a new section at the top (after # Changelog):

markdown

## [X.Y.Z] - YYYY-MM-DD

- Description of change [#123]

Use the format ## [X.Y.Z] - YYYY-MM-DD with no v prefix. Prefix breaking changes with **BREAKING**.

4. Commit

bash

git add lib/schked/version.rb CHANGELOG.md
git commit -m "chore: bump version to X.Y.Z"

5. Push to master

bash

git push origin master

6. Tag and push the tag

bash

git tag vX.Y.Z
git push origin vX.Y.Z

7. CI does the rest

Pushing the vX.Y.Z tag triggers .github/workflows/release.yml which:

Builds the gem and pushes to RubyGems via rubygems/release-gem action (Trusted Publishing — no API keys needed)
bundle exec rake release runs under the hood — skips tag creation since it already exists (already_tagged? guard)
Extracts changelog section via scripts/release_notes.sh
Creates a GitHub Release with the changelog as notes and .gem as asset

Troubleshooting

rake release fails with "not clean": Ensure all changes are committed before pushing the tag
Trusted Publishing fails: Verify the publisher is correctly configured on rubygems.org and the workflow name matches exactly release.yml
Tag already exists: If you need to re-release, delete the tag locally and remotely first (git tag -d vX.Y.Z && git push origin :refs/tags/vX.Y.Z)

Files

Just SKILL.md in .agents/skills/release of bibendi/schked.

Open the folder on GitHubat commit c1f45ac

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 skillbibendi/schked	138	—	~670	Automated safety check: Notes	MIT	1 mo ago
ClawRouter Release ChecklistBlockRunAI/ClawRouter	6.6k	—	~1.4k	Automated safety check: Pass	MIT	2 days ago
AnyDrag Release RoutineXueshiQiao/AnyDrag	227	—	~2.6k	Automated safety check: Pass	GPL-3.0	3 days ago
ReleaseEmertonData/glide	119	—	~2k	Automated safety check: Pass	Custom licence	yesterday
ClickUp CLI Release Processkrodak/clickup-cli	120	—	~906	Automated safety check: Warn	MIT	yesterday
OpenWork Release Processdifferent-ai/openwork	24k	—	~2.3k	Automated safety check: Pass	Custom licence	today

Similar skills

ClawRouter Release Checklist
BlockRunAI/ClawRouter
Walks the agent through every ClawRouter release step in order, from the version bump and changelog entry to build, tests, npm publish, git tag and GitHub release.
6.6k GitHub stars~1.4k tokensUpdated 2 days ago
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 3 days ago
DevelopmentAuto-check passed
Release
EmertonData/glide
Automates the GLIDE release process end-to-end: bumps the version, edits CHANGELOG, opens a release PR, triggers TestPyPI, creates the git tag, and creates the GitHub release.
119 GitHub stars~2k tokensUpdated yesterday
DevelopmentAuto-check passed
ClickUp CLI Release Process
krodak/clickup-cli
Walks through releasing a new version of clickup-cli: pre-release checks, version bump, tagging, CI watch, release notes and the Homebrew update.
120 GitHub stars~906 tokensUpdated yesterday
DevOps & CloudAuto-check: warnings
OpenWork Release Process
different-ai/openwork
Cuts an OpenWork desktop release through a tag-driven GitHub Actions workflow that makes no commits, with pre-tag checks on open fix PRs and verification afterward.
24k GitHub stars~2.3k tokensUpdated today
DevOps & CloudAuto-check passed
Draft Release Notes
jamiepine/voicebox
Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.
57k GitHub stars~941 tokensUpdated yesterday
DevelopmentAuto-check passed

Questions about Release

What does Release do?

Guides through the full gem release process — bump version, update CHANGELOG, tag, push to RubyGems, and create GitHub Release. Release is an agent skill from bibendi/schked. Guides through the full gem release process — bump version, update CHANGELOG, tag, push to RubyGems, and create GitHub Release.

When should I use Release?

Release fits situations like: user asks to release a new version; tasks that involve Deployment; tasks that involve Changelog and release notes.

How do I install Release in Claude Code?

Run `npx skills add bibendi/schked --skill release -a claude-code`. Or copy the skill folder (.agents/skills/release in bibendi/schked) 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 bibendi/schked --skill release -a codex`. Or copy the skill folder (.agents/skills/release in bibendi/schked) 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 bibendi/schked --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 bundle). Its frontmatter pre-approves these tools: Bash.

Does Release access the network?

SKILL.md names 2 domains. In commands or code: rubygems.org; the agent is likely to contact it when it follows the instructions. As links in the text: semver.org. This is read from the text; nothing was executed.

Is Release safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. 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 670 tokens (SKILL.md is roughly 2.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: ClawRouter Release Checklist (BlockRunAI/ClawRouter, 6.6k stars), AnyDrag Release Routine (XueshiQiao/AnyDrag, 227 stars), Release (EmertonData/glide, 119 stars) and ClickUp CLI Release Process (krodak/clickup-cli, 120 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release?

bibendi (a GitHub user) maintains it in bibendi/schked, which has 138 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on August 30, 2026.

Source: bibendi/schked 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

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Gem Release Process

Overview

Prerequisites

Step-by-step

1. Determine new version

2. Update version file

3. Update CHANGELOG

4. Commit

5. Push to master

6. Tag and push the tag

7. CI does the rest

Troubleshooting

Files

Compare with similar skills

Similar skills

ClawRouter Release Checklist

AnyDrag Release Routine

Release

ClickUp CLI Release Process

OpenWork Release Process

Draft Release Notes

More from bibendi/schked

Schked

Related

Questions about Release