Agent skill

Cobang Release

A skill your agent uses when preparing a new CoBang release: reading current version from meson.build, choosing the next version, inferring changes from Git history, and adding a release entry in…

GPL-3.0Auto-check passedDevelopment

Install Cobang Release

skills CLI

$ npx skills add hongquan/CoBang --skill cobang-release -a claude-code

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

GitHub CLI

$ gh skill install hongquan/CoBang cobang-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/hongquan/CoBang.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/cobang-release .claude/skills/cobang-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 "cobang-release" agent skill from https://github.com/hongquan/CoBang/tree/main/.agents/skills/cobang-release into .claude/skills/cobang-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cobang-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/hongquan/CoBang/tree/main/.agents/skills/cobang-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 hongquan/CoBang --skill cobang-release -a codex

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

GitHub CLI

$ gh skill install hongquan/CoBang cobang-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/hongquan/CoBang.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/cobang-release .agents/skills/cobang-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 "cobang-release" agent skill from https://github.com/hongquan/CoBang/tree/main/.agents/skills/cobang-release into .agents/skills/cobang-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cobang-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 hongquan/CoBang --skill cobang-release -a cursor

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

GitHub CLI

$ gh skill install hongquan/CoBang cobang-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/hongquan/CoBang.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/cobang-release .cursor/skills/cobang-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 "cobang-release" agent skill from https://github.com/hongquan/CoBang/tree/main/.agents/skills/cobang-release into .cursor/skills/cobang-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cobang-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/hongquan/CoBang.git --path .agents/skills/cobang-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 hongquan/CoBang --skill cobang-release -a gemini-cli

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

GitHub CLI

$ gh skill install hongquan/CoBang cobang-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/hongquan/CoBang.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/cobang-release .gemini/skills/cobang-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 "cobang-release" agent skill from https://github.com/hongquan/CoBang/tree/main/.agents/skills/cobang-release into .gemini/skills/cobang-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cobang-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 hongquan/CoBang cobang-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 hongquan/CoBang --skill cobang-release -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/hongquan/CoBang.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/cobang-release .github/skills/cobang-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 "cobang-release" agent skill from https://github.com/hongquan/CoBang/tree/main/.agents/skills/cobang-release into .github/skills/cobang-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cobang-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 hongquan/CoBang --skill cobang-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 hongquan/CoBang cobang-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/hongquan/CoBang.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/cobang-release .opencode/skills/cobang-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 "cobang-release" agent skill from https://github.com/hongquan/CoBang/tree/main/.agents/skills/cobang-release into .opencode/skills/cobang-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cobang-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: cobang-release
GitHub stars: 354
Token cost: ~1.3k tokens
SKILL.md length: 409 words
Files: 1
Skills in repo: 2
Repo updated: Oct 4, 2026
First seen: Oct 7, 2026
Licence: GPL-3.0

At a glance

A skill your agent uses when preparing a new CoBang release: reading current version from meson.build, choosing the next version, inferring changes from Git history, and adding a release entry in…

Works in 8 steps: Read current version from meson.build → Ask the user what version we are about… → Determine the Git revision range for the… → …
Preparing a new CoBang release: reading current version from meson.build
SKILL.md covers When to use, Workflow, Example: release after v2.5.2 and What NOT to do, plus 1 more section
Calls git

What it does

Cobang Release is an agent skill from hongquan/CoBang. Use when preparing a new CoBang release: reading current version from meson.build, choosing the next version, inferring changes from Git history, and adding a release entry in the AppStream metainfo file.

Its SKILL.md is about 1.3k 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 Git workflow. It works with Python. The repository describes itself as: A QR code scanner desktop app for Linux. The licence is GPL-3.0.

When your agent uses it

Preparing a new CoBang release: reading current version from meson.build
Choosing the next version
Inferring changes from Git history
Adding a release entry in the AppStream metainfo file

Example prompts

“/cobang-release”

Requirements

Python 3

Workflow steps

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

Read current version from meson.build
Ask the user what version we are about to make
Determine the Git revision range for the changelog
Infer changes from the commit history
Pick a release date
Add the entry in the metainfo template
Verify with appstreamcli
Optional: validate the whole meson data test target

What it can do on your machine

Read from SKILL.md and the folder at commit 9278c46. 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
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, 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

Cobang Release loads about 1.3k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 409 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~55
When it runs · the whole SKILL.md, loaded when a task matches: ~1.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 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 hongquan/CoBang at commit 9278c46, republished under its GPL-3.0 licence (© hongquan). 409 words, ~1,251 tokens.

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

name: cobang-release
description: Use when preparing a new CoBang release: reading current version from meson.build, choosing the next version, inferring changes from Git history, and adding a release entry in the AppStream metainfo file.

cobang-release — Guide for making a CoBang release

When to use

Whenever the user wants to cut a new release for CoBang. This includes:

Preparing release metadata before tagging.
Adding a <release> entry to data/vn.hoabinh.quan.CoBang.metainfo.xml.in.
Verifying the version in meson.build matches the upcoming release.

Workflow

1. Read current version from `meson.build`

Open meson.build and find the version: key in the project() call.

Example: meson.build

meson

project(
  'cobang',
  version: '2.5.2',
  ...
)

Treat this value as the current released version.

2. Ask the user what version we are about to make

Ask explicitly for the next version string, for example: 2.6.0 or 2.5.3. Use the question tool to avoid assumptions.

3. Determine the Git revision range for the changelog

Use the current version as the starting tag. CoBang tags are prefixed with v, so the range is:

bash

git log v<CURRENT_VERSION>..HEAD --oneline --decorate

Example:

bash

git log v2.5.2..HEAD --oneline --decorate

4. Infer changes from the commit history

Read every commit message in the range. Group and summarize them into a few user-facing bullet points for AppStream.

Guidelines:

Use plain English in the style of existing <release> entries.
Keep bullets short (one sentence each, <p>...</p>).
Merge related commits: if several commits all refine one feature, describe the feature once.
Mention user-visible behavior only; omit internal refactor chores unless they affect behavior.
If many commits exist after the last tag, focus on the most meaningful 3–6 changes.

Example from v2.0.0:

xml

<release version="2.0.0" date="YYYY-MM-DD" urgency="medium">
  <description translate="no">
    <p>Add QR code generator.</p>
    <p>Add Croatian language.</p>
  </description>
</release>

5. Pick a release date

Use today's date in YYYY-MM-DD format.

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

6. Add the `<release>` entry in the metainfo template

Open data/vn.hoabinh.quan.CoBang.metainfo.xml.in.

Insert the new <release> block as the first child of the <releases> element, above existing <release> entries.

Format:

xml

  <releases>
    <release version="NEW_VERSION" date="YYYY-MM-DD" urgency="medium">
      <description translate="no">
        <p>Summary of change 1.</p>
        <p>Summary of change 2.</p>
      </description>
    </release>
    <!-- existing releases follow -->
  </releases>

Use urgency="medium" unless there is a compelling reason to use high or low.

7. Verify with `appstreamcli`

Run:

bash

appstreamcli validate --no-net --explain data/vn.hoabinh.quan.CoBang.metainfo.xml.in

If validation fails, fix the XML and rerun.

8. Optional: validate the whole meson data test target

If the build directory exists:

bash

meson test -C builddir --suite data

This runs the AppStream validation test defined in data/meson.build.

Example: release after v2.5.2

Given commits since v2.5.2:

text

331ccdc Fix invalid property in Blueprint file
0298822 Switch build docs to just commands and refine QR preview pane layout
4b1332f Polish QR preview pane controls and add empty-state placeholder
3b68047 Let users pick a saved Wi-Fi network for QR generation
fe27fde Rename properties
13cc7e8 Replace generator page with redesigned form/preview layout
a2fb714 Rename Generator to OldGenerator to prepare for new design of Generator
32800a3 Add gtk-signal-result skill for GTK child-to-parent communication
c46cea6 Simplify ruff pre-commit hooks
2de54d1 Resolve type-checker errors with walrus operator and type narrowing
27bd0b2 Reorganize Blueprint files
acb555b Reformat Python code

If the user chooses 2.6.0, the resulting entry could be:

xml

    <release version="2.6.0" date="2026-07-21" urgency="medium">
      <description translate="no">
        <p>Redesign QR code generator with live preview and empty-state placeholder.</p>
        <p>Let users generate QR codes from saved Wi-Fi networks.</p>
        <p>Polish generator controls and preview pane layout.</p>
      </description>
    </release>

What NOT to do

Do not bump meson.build version: to the new value yet. Only update the metainfo release list at this stage.
Do not commit or push changes unless the user explicitly asks for it.
Do not add release notes for commits that are purely internal (lint, reformat, renaming private symbols, build docs).

Notes

The file path is data/vn.hoabinh.quan.CoBang.metainfo.xml.in, not the generated .metainfo.xml.
Existing entries use description translate="no"; preserve that attribute.
The release text uses <p> paragraphs only; do not use Markdown or lists.

Files

Just SKILL.md in .agents/skills/cobang-release of hongquan/CoBang.

Open the folder on GitHubat commit 9278c46

Compare with similar skills

Cobang 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.

Cobang Release compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Cobang Release this skillhongquan/CoBang	354	—	~1.3k	Automated safety check: Pass	GPL-3.0	6 days ago
Kedro Babysitkedro-org/kedro	11k	—	~4k	Automated safety check: Pass	Custom licence	2 days ago
Skyvern Version BumpSkyvern-AI/skyvern	23k	—	~1k	Automated safety check: Notes	AGPL-3.0	yesterday
Saleor Commit Workflowsaleor/saleor	23k	—	~575	Automated safety check: Pass	BSD-3-Clause	yesterday
pybind11 Release Preparationpybind/pybind11	18k	—	~1.7k	Automated safety check: Pass	Custom licence	2 days ago
pybind11 Release Publicationpybind/pybind11	18k	—	~2.5k	Automated safety check: Pass	Custom licence	2 days ago

Similar skills

Kedro Babysit
kedro-org/kedro
Run Kedro's local lint / format / type-check / tests on changed files (uses the project's pre-commit hooks, ruff, mypy, pytest, lint-imports, detect-secrets, Make targets — in the right venv), or…
11k GitHub stars~4k tokensUpdated 2 days ago
DevelopmentAuto-check passed
Skyvern Version Bump
Skyvern-AI/skyvern
Walks through a Skyvern open-source release bump: update the version, rebuild the Python and TypeScript SDKs with Fern, commit, and open a pull request.
23k GitHub stars~1k tokensUpdated yesterday
DevelopmentAuto-check: notes
Saleor Commit Workflow
saleor/saleor
Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.
23k GitHub stars~575 tokensUpdated yesterday
DevelopmentAuto-check passed
pybind11 Release Preparation
pybind/pybind11
Opens the pybind11 release-preparation pull request: picking the release base, bumping the version in common.h and integrating the changelog, following docs/release.rst.
18k GitHub stars~1.7k tokensUpdated 2 days ago
DevelopmentAuto-check passed
pybind11 Release Publication
pybind/pybind11
Walks a maintainer through publishing a pybind11 release after the preparation PR merges, with preflight checks, confirmations before each push and a GitHub release.
18k GitHub stars~2.5k tokensUpdated 2 days ago
DevelopmentAuto-check passed
Git History Bug Audit
ben-manes/caffeine
Audits a module by walking its git history commit by commit, tracking unresolved issues forward, and reporting the ones that survive to HEAD as findings.
18k GitHub stars~3.3k tokensUpdated today
DevelopmentAuto-check passed

Questions about Cobang Release

What does Cobang Release do?

A skill your agent uses when preparing a new CoBang release: reading current version from meson.build, choosing the next version, inferring changes from Git history, and adding a release entry in…. Cobang Release is an agent skill from hongquan/CoBang.build, choosing the next version, inferring changes from Git history, and adding a release entry in the AppStream metainfo file.

When should I use Cobang Release?

Cobang Release fits situations like: preparing a new CoBang release: reading current version from meson.build; choosing the next version; inferring changes from Git history; adding a release entry in the AppStream metainfo file.

How do I install Cobang Release in Claude Code?

Run `npx skills add hongquan/CoBang --skill cobang-release -a claude-code`. Or copy the skill folder (.agents/skills/cobang-release in hongquan/CoBang) into .claude/skills/cobang-release in your project. Claude Code loads it when a task matches its description.

How do I install Cobang Release in Codex?

Run `npx skills add hongquan/CoBang --skill cobang-release -a codex`. Or copy the skill folder (.agents/skills/cobang-release in hongquan/CoBang) into .agents/skills/cobang-release in your project. Codex loads it when a task matches its description.

Can I use Cobang 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 hongquan/CoBang --skill cobang-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/cobang-release, .gemini/skills/cobang-release, .github/skills/cobang-release and .opencode/skills/cobang-release in your project.

What does Cobang Release need to run?

Going by SKILL.md and its folder, Cobang Release needs the command-line tools its instructions call (git). Our summary lists: Python 3.

Does Cobang Release access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Cobang 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 Cobang Release use?

Cobang Release is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cobang Release use?

About 1.3k tokens (SKILL.md is roughly 5k 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 Cobang Release?

Skills that share tags, products or a category with Cobang Release: Kedro Babysit (kedro-org/kedro, 11k stars), Skyvern Version Bump (Skyvern-AI/skyvern, 23k stars), Saleor Commit Workflow (saleor/saleor, 23k stars) and pybind11 Release Preparation (pybind/pybind11, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cobang Release?

hongquan (a GitHub user) maintains it in hongquan/CoBang, which has 354 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 4, 2026.

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

Install Cobang 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

cobang-release — Guide for making a CoBang release

When to use

Workflow

1. Read current version from meson.build

2. Ask the user what version we are about to make

3. Determine the Git revision range for the changelog

4. Infer changes from the commit history

5. Pick a release date

6. Add the <release> entry in the metainfo template

7. Verify with appstreamcli

8. Optional: validate the whole meson data test target

Example: release after v2.5.2

What NOT to do

Notes

Files

Compare with similar skills

Similar skills

Kedro Babysit

Skyvern Version Bump

Saleor Commit Workflow

pybind11 Release Preparation

pybind11 Release Publication

Git History Bug Audit

More from hongquan/CoBang

Gtk Signal Result

Related

Questions about Cobang Release

1. Read current version from `meson.build`

6. Add the `<release>` entry in the metainfo template

7. Verify with `appstreamcli`