Handsontable Demo Page Generator
handsontable/handsontable
Builds two throwaway HTML test pages for a Handsontable pull request, one on the released CDN version and one on the local build, to compare behavior side by side.
Cut and publish a project release — verify or derive the version number (patch/minor/major) from the changelog and accumulated changes, follow the repo's own branch and versioning strategy, rebase…
$ npx skills add akitaonrails/my-skills --skill release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install akitaonrails/my-skills release --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/akitaonrails/my-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/release .claude/skills/release && rm -rf skills-srcUse ~/.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/
Install the "release" agent skill from https://github.com/akitaonrails/my-skills/tree/master/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 install https://github.com/akitaonrails/my-skills/tree/master/releaseType 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.
$ npx skills add akitaonrails/my-skills --skill release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install akitaonrails/my-skills release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/akitaonrails/my-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/release .agents/skills/release && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release" agent skill from https://github.com/akitaonrails/my-skills/tree/master/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.
$ npx skills add akitaonrails/my-skills --skill release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install akitaonrails/my-skills release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/akitaonrails/my-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/release .cursor/skills/release && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release" agent skill from https://github.com/akitaonrails/my-skills/tree/master/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 https://github.com/akitaonrails/my-skills.git --path release--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add akitaonrails/my-skills --skill release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install akitaonrails/my-skills release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/akitaonrails/my-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/release .gemini/skills/release && rm -rf skills-srcUse ~/.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/
Install the "release" agent skill from https://github.com/akitaonrails/my-skills/tree/master/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.
$ gh skill install akitaonrails/my-skills releaseInstalls 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).
$ npx skills add akitaonrails/my-skills --skill release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/akitaonrails/my-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/release .github/skills/release && rm -rf skills-srcUse ~/.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/
Install the "release" agent skill from https://github.com/akitaonrails/my-skills/tree/master/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.
$ npx skills add akitaonrails/my-skills --skill release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install akitaonrails/my-skills release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/akitaonrails/my-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/release .opencode/skills/release && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release" agent skill from https://github.com/akitaonrails/my-skills/tree/master/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.
releaseCut and publish a project release — verify or derive the version number (patch/minor/major) from the changelog and accumulated changes, follow the repo's own branch and versioning strategy, rebase…
Release is an agent skill from akitaonrails/my-skills. Cut and publish a project release — verify or derive the version number (patch/minor/major) from the changelog and accumulated changes, follow the repo's own branch and versioning strategy, rebase release branches from main/master before tagging, run pr-post-audit when commits have accumulated since the last release, and tag/publish only on green CI at the exact release SHA. Use when the user asks to release, cut/ship/publish/tag a version ("release 2.1", "cut a minor", "ship a patch", "publish the release"), or…
Its SKILL.md is about 1.9k 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 and QA and bug reports. It works with Git and GitHub. The repository describes itself as: akitaonrails' personal skills (not tailored for general usage).
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 285ca82. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
gitghFrom the folder's file list and the shell code blocks in SKILL.md.
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.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Release loads about 1.9k tokens when it runs. Until then it costs about 160 tokens; SKILL.md has 961 words of instructions outside code blocks.
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.
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.
Without a licence we can't republish the file, so here is its outline and opening line. It has 961 words (~1,937 tokens).
“Turn an accumulated mainline into a tagged, published version. This skill is the explicit "ship it" step that github-resolution deliberately separates from resolving tickets: it runs only when the user asks for a release.”
Just SKILL.md in release of akitaonrails/my-skills.
Open the folder on GitHubat commit 285ca82
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release this skillakitaonrails/my-skills | 216 | — | ~1.9k | Automated safety check: Pass | None | |
| Handsontable Demo Page Generatorhandsontable/handsontable | 22k | — | ~1.8k | Automated safety check: Pass | Custom licence | |
| Draft Release Notesjamiepine/voicebox | 57k | — | ~941 | Automated safety check: Pass | MIT | |
| Mole Release Notes Publishertw93/Mole | 70k | — | ~1.9k | Automated safety check: Pass | GPL-3.0 | |
| Release Bumpjamiepine/voicebox | 57k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT |
handsontable/handsontable
Builds two throwaway HTML test pages for a Handsontable pull request, one on the released CDN version and one on the local build, to compare behavior side by side.
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.
tw93/Mole
Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.
jamiepine/voicebox
Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
redis/go-redis
Prepares a go-redis release locally: picks the next semver, gathers merged PRs, writes the RELEASE-NOTES entry and bumps versions, without publishing.
akitaonrails/my-skills
Adversarial fact-checking of the user's articles and essays (typically blog posts from akitaonrails-hugo, any markdown/text file), verifying every claim against online primary sources via cheap…
akitaonrails/my-skills
Generate dark-themed cost-vs-score bubble scatter charts and score/(costtime) value-ranking bar charts for a blog post comparing LLM benchmark results (or any dataset with a score/cost/time shape)…
akitaonrails/my-skills
Generate comprehensive hierarchical codemaps for UNFAMILIAR repositories.
akitaonrails/my-skills
Clone important project dependency source code into an ignored local workspace so OpenCode can inspect library internals.
akitaonrails/my-skills
Execute the approved outcomes of a pr-audit and/or iss-audit — fix or adjust everything the audit found necessary before merging, verify no regressions, cover every new behavior with unit tests…
akitaonrails/my-skills
Post-refactor clean-code check after recent refactors or a few merged PRs.
Categories
Cut and publish a project release — verify or derive the version number (patch/minor/major) from the changelog and accumulated changes, follow the repo's own branch and versioning strategy, rebase…. Release is an agent skill from akitaonrails/my-skills. Cut and publish a project release — verify or derive the version number (patch/minor/major) from the changelog and accumulated changes, follow the repo's own branch and versioning strategy, rebase release branches from main/master before tagging, run pr-post-audit when commits have accumulated since the last release, and tag/publish only on green CI at the exact release SHA.
Release fits situations like: the user asks to release; cut/ship/publish/tag a version (release 2.1; publish the release); finalize a changelog for a version.
Run `npx skills add akitaonrails/my-skills --skill release -a claude-code`. Or copy the skill folder (release in akitaonrails/my-skills) into .claude/skills/release in your project. Claude Code loads it when a task matches its description.
Run `npx skills add akitaonrails/my-skills --skill release -a codex`. Or copy the skill folder (release in akitaonrails/my-skills) into .agents/skills/release in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add akitaonrails/my-skills --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.
Going by SKILL.md and its folder, Release needs the command-line tools its instructions call (git and gh).
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.
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.
No licence was found for Release or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Release: Handsontable Demo Page Generator (handsontable/handsontable, 22k stars), Draft Release Notes (jamiepine/voicebox, 57k stars), Mole Release Notes Publisher (tw93/Mole, 70k stars) and Release Bump (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
akitaonrails (a GitHub user) maintains it in akitaonrails/my-skills, which has 216 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on September 23, 2026.
Source: akitaonrails/my-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.