Agent skill

Release

Run the Harnss release workflow — review staged diff, bump version, commit, tag, push, and create a GitHub release.

MITAuto-check: notesDevelopment

Install Release

skills CLI

$ npx skills add OpenSource03/harnss --skill release -a claude-code

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

GitHub CLI

$ gh skill install OpenSource03/harnss 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/OpenSource03/harnss.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/OpenSource03/harnss/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/OpenSource03/harnss/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 OpenSource03/harnss --skill release -a codex

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

GitHub CLI

$ gh skill install OpenSource03/harnss 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/OpenSource03/harnss.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/OpenSource03/harnss/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 OpenSource03/harnss --skill release -a cursor

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

GitHub CLI

$ gh skill install OpenSource03/harnss 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/OpenSource03/harnss.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/OpenSource03/harnss/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/OpenSource03/harnss.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 OpenSource03/harnss --skill release -a gemini-cli

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

GitHub CLI

$ gh skill install OpenSource03/harnss 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/OpenSource03/harnss.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/OpenSource03/harnss/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 OpenSource03/harnss 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 OpenSource03/harnss --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/OpenSource03/harnss.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/OpenSource03/harnss/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 OpenSource03/harnss --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 OpenSource03/harnss 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/OpenSource03/harnss.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/OpenSource03/harnss/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: 382
Token cost: ~1.1k tokens
SKILL.md length: 429 words
Files: 2 (incl. references)
Skills in repo: 1
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Run the Harnss release workflow — review staged diff, bump version, commit, tag, push, and create a GitHub release.

Works in 5 steps: Pre-flight Checks → Version Bump → Commit → …
Bumping version
SKILL.md covers Step 1: Pre-flight Checks, Step 2: Version Bump, Step 3: Commit and Step 4: Tag & Push, plus 2 more sections
Calls git, npm and pnpm

What it does

Release is an agent skill from OpenSource03/harnss. Run the Harnss release workflow — review staged diff, bump version, commit, tag, push, and create a GitHub release. Use when releasing, bumping version, tagging, or creating a release. Argument: major, minor, or patch.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/release-notes-template.md`).

It sits in Development. It works with GitHub, Google Gemini, OpenAI and npm. The repository describes itself as: Open-source, desktop client/UI build to harness Claude Code, Codex and any other Agent accepting Agent Client Protocol. Run multiple AI coding agents side by side with rich tool… The licence is MIT.

When your agent uses it

Bumping version
Creating a release

Example prompts

“/release”

Workflow steps

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

Pre-flight Checks
Version Bump
Commit
Tag & Push
GitHub Release

What it can do on your machine

Read from SKILL.md and the folder at commit dc1dfd8. 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
- npm
- pnpm
- 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, npm, pnpm 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 1.1k tokens when it runs, and up to ~2.3k if it reads all its reference files. Until then it costs about 57 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: ~57
When it runs · the whole SKILL.md, loaded when a task matches: ~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~2.3k

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.

NoteMentions a .env fileSKILL.md:24

- Files that shouldn't be committed (`.env`, credentials, large binaries)

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 OpenSource03/harnss at commit dc1dfd8, republished under its MIT licence (© OpenSource03). 429 words, ~1,092 tokens.

Download SKILL.mdSave it as .claude/skills/release/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: release
description: Run the Harnss release workflow — review staged diff, bump version, commit, tag, push, and create a GitHub release. Use when releasing, bumping version, tagging, or creating a release. Argument: major, minor, or patch.

Harnss Release Workflow

Run the full release pipeline. Bump type is passed as $ARGUMENTS (major, minor, or patch).

Step 1: Pre-flight Checks

Run these commands and read every line of output:

bash

git status
git diff --cached --stat
git diff --cached

If the diff is too large to read in one shot, read it in chunks (e.g., per-directory or line ranges). You must read the entire diff before proceeding.

Review for:

Test files, scratch files, temp files, debug artifacts (e.g., test-*.ts, scratch.*, *.tmp, random-*.md)
Files that shouldn't be committed (.env, credentials, large binaries)

If you find any:

Unstage or remove them
Tell the user what you removed

If there are no staged changes but unstaged changes exist, ask the user if they want to stage anything first. If the working tree is completely clean (nothing to release), tell the user and stop.

Step 2: Version Bump

Determine new version

Read the current version from package.json (the "version" field)
Get the latest tag: git tag --sort=-v:refname | head -1
Parse the current version as MAJOR.MINOR.PATCH
Apply the bump type from $ARGUMENTS:
- major → (MAJOR+1).0.0
- minor → MAJOR.(MINOR+1).0
- patch → MAJOR.MINOR.(PATCH+1)
If $ARGUMENTS is empty or invalid, ask the user which bump type they want

Check for SDK updates

bash

npm view @anthropic-ai/Codex-agent-sdk version

Compare with the version in package.json under dependencies["@anthropic-ai/Codex-agent-sdk"] (strip the ^ prefix for comparison). If a newer version exists, update the dependency version (keep the ^ prefix) and tell the user.

Apply changes

Edit package.json to set the new version number
Stage it: git add package.json

If the SDK was updated, also run:

bash

pnpm install
git add package.json pnpm-lock.yaml

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

Step 3: Commit

Choose the commit message based on what's staged:

Feature/fix changes staged (not just version bump)

feat: short summary (2-4 key themes)

- Change description 1
- Change description 2
- ...

Co-Authored-By: Codex Opus 4.6 (1M context) <noreply@anthropic.com>

Use fix: instead of feat: if all changes are bug fixes.

Only version bump staged

chore: bump version to X.Y.Z

Co-Authored-By: Codex Opus 4.6 (1M context) <noreply@anthropic.com>

If the SDK was also updated:

chore: bump version to X.Y.Z and update Codex-agent-sdk to A.B.C

Co-Authored-By: Codex Opus 4.6 (1M context) <noreply@anthropic.com>

Always use a HEREDOC

bash

git commit -m "$(cat <<'EOF'
<message here>

Co-Authored-By: Codex Opus 4.6 (1M context) <noreply@anthropic.com>
EOF
)"

Step 4: Tag & Push

bash

git tag vX.Y.Z HEAD
git push origin master && git push origin vX.Y.Z

If push fails, report the error and stop.

Step 5: GitHub Release

Gather context

Get the previous release tag:

bash

git tag --sort=-v:refname | head -2 | tail -1

Read the full diff and commit log since the previous release:

bash

git log v{prev}...HEAD --oneline
git diff v{prev}...HEAD --stat
git diff v{prev}...HEAD

Read ALL of this output. For the full diff, read it in chunks if needed — every line matters for writing accurate release notes.

Write release notes

Load the template from references/release-notes-template.md and follow its format exactly.

Create the release

bash

gh release create vX.Y.Z --title "vX.Y.Z — Short Descriptive Phrase" --notes "$(cat <<'EOF'
<release notes>
EOF
)"

The title uses an em dash (—), not a hyphen.

Output the release URL when done so the user can verify.

Important Notes

Never skip reading the full diff in Step 1. Every line matters.
The Co-Authored-By trailer is mandatory on every commit.
Repo: https://github.com/OpenSource03/harnss
Main branch: master
Changelog URL format: https://github.com/OpenSource03/harnss/compare/v{prev}...v{current}
Package manager: pnpm (never use npm or yarn for installs)

Files

SKILL.md and 1 other file (references) in .agents/skills/release of OpenSource03/harnss.

SKILL.md
references/release-notes-template.md

Open the folder on GitHubat commit dc1dfd8

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 skillOpenSource03/harnss	382	—	~1.1k	Automated safety check: Notes	MIT	yesterday
Release ExtensionYorick-Ryu/deep-share	144	—	~1.3k	Automated safety check: Pass	Custom licence	3 days ago
Publish ReleaseAyuilos/Miffan	192	—	~635	Automated safety check: Pass	AGPL-3.0	yesterday
Embeddings via 9Routerdecolua/9router	30k	—	~604	Automated safety check: Pass	MIT	7 days ago
Agentic GitHub Actions Auditortrailofbits/skills	7.4k	6 repos	~5.4k	Automated safety check: Notes	CC-BY-SA-4.0	today
Get API Docs with chubandrewyng/context-hub	14k	2 repos	~775	Automated safety check: Pass	MIT	4 mo ago

Similar skills

Release Extension
Yorick-Ryu/deep-share
Release browser extensions or similar small packaged apps by upgrading a semantic version, packaging build artifacts, creating a git commit and tag, pushing to the remote, and publishing a GitHub…
144 GitHub stars~1.3k tokensUpdated 3 days ago
DevelopmentAuto-check passed
Publish Release
Ayuilos/Miffan
Publish a GitHub release for this fork, with a bilingual changelog that separates fork-owned changes from changes introduced by upstream merges.
192 GitHub stars~635 tokensUpdated yesterday
MobileAuto-check passed
Embeddings via 9Router
decolua/9router
Generates vector embeddings through the 9Router /v1/embeddings endpoint, using models from providers such as OpenAI, Gemini, Mistral and Voyage for RAG and semantic search.
30k GitHub stars~604 tokensUpdated 7 days ago
AI & LLM EngineeringAuto-check passed
Agentic GitHub Actions Auditor
trailofbits/skills
Official
Statically audits GitHub Actions workflows that run AI coding agents, tracing attacker-controlled input to agent prompts and flagging unsafe sandbox, trigger and allowlist settings.
7.4k GitHub starsUsed in 6 repos~5.4k tokens
SecurityAuto-check: notes
Get API Docs with chub
andrewyng/context-hub
Fetches current documentation for third-party APIs and SDKs with the chub CLI before the agent writes code against them, instead of relying on remembered API shapes.
14k GitHub starsUsed in 2 repos~775 tokens
DevelopmentAuto-check passed
Open Code Review CLI
alibaba/open-code-review
Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.
44k GitHub stars~3.1k tokensUpdated 2 days ago
DevelopmentAuto-check passed

Works with

Questions about Release

What does Release do?

Run the Harnss release workflow — review staged diff, bump version, commit, tag, push, and create a GitHub release. Release is an agent skill from OpenSource03/harnss. Run the Harnss release workflow — review staged diff, bump version, commit, tag, push, and create a GitHub release.

When should I use Release?

Release fits situations like: bumping version; creating a release.

How do I install Release in Claude Code?

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

Does Release access the network?

SKILL.md contains no URLs. Its commands use git, npm 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 notes only (mentions a .env file), 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 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.2k tokens, read only when the agent opens those files.

What are the alternatives to Release?

Skills that share tags, products or a category with Release: Release Extension (Yorick-Ryu/deep-share, 144 stars), Publish Release (Ayuilos/Miffan, 192 stars), Embeddings via 9Router (decolua/9router, 30k stars) and Agentic GitHub Actions Auditor (trailofbits/skills, 7.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release?

OpenSource03 (a GitHub user) maintains it in OpenSource03/harnss, which has 382 GitHub stars. The repository was last updated on October 6, 2026.

Source: OpenSource03/harnss 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

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Harnss Release Workflow

Step 1: Pre-flight Checks

Step 2: Version Bump

Determine new version

Check for SDK updates

Apply changes

Step 3: Commit

Feature/fix changes staged (not just version bump)

Only version bump staged

Always use a HEREDOC

Step 4: Tag & Push

Step 5: GitHub Release

Gather context

Write release notes

Create the release

Important Notes

Files

Compare with similar skills

Similar skills

Release Extension

Publish Release

Embeddings via 9Router

Agentic GitHub Actions Auditor

Get API Docs with chub

Open Code Review CLI

Related

Questions about Release