New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Coffee GB Release

by trekawek in trekawek/coffee-gb

Releases the current Coffee GB Maven snapshot through the GitHub Maven release workflow, then verifies and curates the tag and GitHub release.

MITAuto-check passedDevelopment

Install Coffee GB Release

skills CLI
$ npx skills add trekawek/coffee-gb --skill release-new-version -a claude-code

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

GitHub CLI
$ gh skill install trekawek/coffee-gb release-new-version --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/trekawek/coffee-gb.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release-new-version .claude/skills/release-new-version && 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/

Facts

Skill name
release-new-version
GitHub stars
1.2k
Token cost
~1.4k tokens
SKILL.md length
713 words
Files
3 (incl. scripts)
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

Releases the current Coffee GB Maven snapshot through the GitHub Maven release workflow, then verifies and curates the tag and GitHub release.

  • Works in 5 steps: Establish the versions → Run Maven release → Build complete release notes → …
  • Publishing a new Coffee GB version
  • SKILL.md covers 1. Establish the versions, 2. Run Maven release, 3. Build complete release notes and 4. Add one screenshot when…, plus 1 more section
  • Runs Python scripts from its folder; calls gh, git and python3

What it does

From a clean, synchronized default branch, the agent runs scripts/versions.py to get the authoritative release version (the root Maven version without -SNAPSHOT), the next development version (last numeric part incremented plus -SNAPSHOT), the coffee-gb tag and the release title. It stops if the version is not a numeric snapshot, the tag or release already exists unexpectedly, or the branch cannot be fast-forwarded cleanly, and it never releases unpushed or divergent work.

It then dispatches the Maven release workflow with those values and watches it to completion before touching the release. Afterwards it verifies the annotated tag, the next-development commit on the default branch and that the GitHub release carries the executable Swing JAR, non-empty and named after the version, while internal validation files stay unattached. The skill goes on to build complete release notes, with an issue screenshot when one is available.

When your agent uses it

  • Publishing a new Coffee GB version
  • Verifying the tag and artifacts after the Maven release workflow runs
  • Curating the GitHub release notes for a Coffee GB release

Example prompts

  • “Release a new Coffee GB version from the default branch.”
  • “Check that the latest Coffee GB release has the Swing JAR attached and the tag points at the right commit.”

Requirements

  • The gh CLI, authenticated, with permission to dispatch the Maven release workflow
  • Python 3 to run scripts/versions.py

Workflow steps

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

  1. Establish the versions
  2. Run Maven release
  3. Build complete release notes
  4. Add one screenshot when possible
  5. Finalize and verify the GitHub release

What it can do on your machine

Read from SKILL.md and the folder at commit 554ea56. 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

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • gh
    • git
    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh and 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

Coffee GB Release loads about 1.4k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 713 words of instructions outside code blocks.

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

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); the scripts in this folder are not scanned.

SKILL.md

The full file from trekawek/coffee-gb at commit 554ea56, republished under its MIT licence (© trekawek). 713 words, ~1,358 tokens.

Download SKILL.mdSave it as .claude/skills/release-new-version/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
release-new-version
description
Release the current Coffee GB Maven snapshot through the GitHub "Maven release" workflow, then verify and curate the resulting tag and GitHub release. Use when asked to publish, cut, or release a new Coffee GB version.

Release New Version

Publish from the repository default branch and leave a verified GitHub release with the executable Swing JAR, complete notes, and an issue screenshot when one is available.

1. Establish the versions

  1. Require a clean working tree and fetch the default branch and tags.
  2. Confirm the local default branch matches its remote. If it is clean and only behind its remote, run git pull --ff-only origin <default-branch> and verify it now matches. Do not release unpushed commits, a branch with divergent history, or an unmerged branch.
  3. Run python3 .agents/skills/release-new-version/scripts/versions.py from the repository root.
  4. Treat its values as authoritative:
    • release version: the current root Maven version without -SNAPSHOT;
    • development version: increment the final numeric component and append -SNAPSHOT;
    • tag: coffee-gb-<release_version>;
    • title: Coffee GB <release_version> (exact capitalization and spacing, with no trailing punctuation);
  5. Stop if the current version is not a numeric Maven snapshot, the tag or release already exists unexpectedly, or the default branch cannot be synchronized by a clean fast-forward.

2. Run Maven release

Dispatch .github/workflows/maven-release.yml on the remote default branch with the calculated values:

bash
gh workflow run "Maven release" --ref <default-branch> \
  -f release_version=<release_version> \
  -f development_version=<development_version>

Find the newly dispatched run, watch it to completion, and inspect failed logs if necessary. Do not create or edit the release while the workflow is still running. The workflow prepares coffee-gb-<release_version>, advances the Maven version, publishes to Maven Central, and currently creates an initial GitHub release.

After success, fetch and verify:

  • the annotated release tag exists remotely and points at the workflow's release commit;
  • the default branch contains the next-development commit and reports <development_version>;
  • the GitHub release is based on the new tag;
  • the executable built at target/checkout/swing/target/coffee-gb-<release_version>.jar is attached as coffee-gb-<release_version>.jar and is non-empty.
  • NATIVE-PACKAGE-MATRIX.properties and SHA256SUMS were used only for internal validation and are not attached to the GitHub release.

3. Build complete release notes

Find the immediately preceding coffee-gb-* release tag. Use the range from that tag (exclusive) through the new tag (inclusive).

Collect all three views before writing the notes:

  • commit history in the tag range, including non-PR commits;
  • PRs merged into the default branch whose merge commits fall in the range;
  • issues explicitly closed by those PRs or commits. Use PR closing references and linked issues; do not claim every issue closed during the date range was fixed by the release.

Use GitHub's generated notes as a starting point, then reconcile them against the collected commits, merged PRs, and fixed issues. Include a concise change summary followed by explicit Merged pull requests and Fixed issues lists; write None when a list is genuinely empty. Link PR and issue numbers, credit contributors, and omit mechanical release commits. Do not invent fixed issues or infer a fix from timing alone.

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

4. Add one screenshot when possible

Inspect fixed issues and their linked PRs for an existing screenshot that demonstrates a visible fix. Prefer the clearest single after-fix image.

  • Reuse an existing GitHub-hosted image when its provenance and meaning are clear.
  • Otherwise, if a suitable local screenshot was produced during the fix, upload it as a release asset and reference it from the notes.
  • Include at most one screenshot and give it a short caption linking the fixed issue.
  • Skip the screenshot if no fixed issue has a meaningful visual result or no usable image exists. Do not delay or fail the release for this optional item.

5. Finalize and verify the GitHub release

Because the workflow creates the initial release, edit that release rather than creating a duplicate. Set its exact title to Coffee GB <release_version> and replace its body with the curated notes. Do not use the lowercase/hyphenated tag form as the title, and do not append a period or other punctuation. If the executable JAR is missing after a successful run, stop and investigate the workflow inconsistency instead of silently substituting an unrelated local build.

Verify with gh release view <tag> --json name,tagName,url,assets,body that:

  • name exactly matches Coffee GB <release_version>, including capitalization and spacing, with no trailing punctuation;
  • tagName matches the new tag;
  • the executable coffee-gb-<release_version>.jar is present exactly once;
  • neither NATIVE-PACKAGE-MATRIX.properties nor SHA256SUMS is present;
  • the body covers commits, merged PRs, and fixed issues;
  • the body contains no Native package signing evidence section;
  • the optional screenshot renders if included.

Report the workflow run, tag, release URL, released version, next development version, and executable asset.

© trekawek, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (scripts) in .agents/skills/release-new-version of trekawek/coffee-gb.

  • SKILL.md
  • agents/openai.yaml
  • scripts/versions.py

Open the folder on GitHubat commit 554ea56

Compare with similar skills

Coffee GB 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.

Coffee GB Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Coffee GB Release this skilltrekawek/coffee-gb1.2k—~1.4kAutomated safety check: PassMIT
Worktrunk Release Workflowmax-sixty/worktrunk9.2k—~6.9kAutomated safety check: PassCustom licence
Kt Search Releasejillesvangurp/kt-search155—~1.2kAutomated safety check: PassMIT
Codex Proxy RS Releasezyycn/codex-proxy-rs780—~327Automated safety check: PassApache-2.0
CI Automationjeremylongshore/tons-of-skills-marketplace2.8k—~1.4kAutomated safety check: NotesMIT
ClickUp CLI Release Processkrodak/clickup-cli123—~906Automated safety check: WarnMIT

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.

    9.2k GitHub stars~6.9k tokensUpdated today
    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

  • Codex Proxy RS Release

    zyycn/codex-proxy-rs

    Plans versions, writes release notes, publishes stable or pre-release builds and recovers from failed releases for Codex Proxy RS, without covering deploys or tag cleanup.

    780 GitHub stars~327 tokensUpdated today
    DevelopmentAuto-check passed

  • CI Automation

    jeremylongshore/tons-of-skills-marketplace

    A skill your agent uses when running GitHub Actions locally, creating task runner recipes, generating changelogs from git history, managing GitHub PRs/issues/releases programmatically, or creating…

    2.8k GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check: notes

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

    123 GitHub stars~906 tokensUpdated 4 days ago
    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

More from trekawek/coffee-gb

  • Game Boy ROM Playthrough Driver

    trekawek/coffee-gb

    Plays an authorized Game Boy or Game Boy Color ROM in one persistent headless Coffee GB session, inspecting frames and keeping an action trace for replay or tests.

    1.2k GitHub stars~1.3k tokensUpdated 9 days ago
    Auto-check passed

  • Gitshot Image Uploader

    trekawek/coffee-gb

    Uploads screenshots and other images from the terminal and returns markdown-ready URLs to embed in GitHub pull requests, issues and comments.

    1.2k GitHub stars~855 tokensUpdated 9 days ago
    Auto-check passed

  • Merge Pull Request

    trekawek/coffee-gb

    Validates a GitHub pull request, rebases away conflicts, waits for required CI on the final commit, merges with rebase and cleans up the topic branch.

    1.2k GitHub stars~903 tokensUpdated 9 days ago
    Auto-check passed

  • Coffee GB Compatibility Fix

    trekawek/coffee-gb

    Takes a Coffee GB compatibility issue from reproduction through a tested fix to an isolated pull request, with issue follow-up and screenshot evidence when possible.

    1.2k GitHub stars~1.4k tokensUpdated 9 days ago
    Auto-check passed

Works with

Categories

Questions about Coffee GB Release

What does Coffee GB Release do?

Releases the current Coffee GB Maven snapshot through the GitHub Maven release workflow, then verifies and curates the tag and GitHub release. py to get the authoritative release version (the root Maven version without -SNAPSHOT), the next development version (last numeric part incremented plus -SNAPSHOT), the coffee-gb tag and the release title. It stops if the version is not a numeric snapshot, the tag or release already exists unexpectedly, or the branch cannot be fast-forwarded cleanly, and it never releases unpushed or divergent work.

When should I use Coffee GB Release?

Coffee GB Release fits situations like: publishing a new Coffee GB version; verifying the tag and artifacts after the Maven release workflow runs; curating the GitHub release notes for a Coffee GB release.

How do I install Coffee GB Release in Claude Code?

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

How do I install Coffee GB Release in Codex?

Run `npx skills add trekawek/coffee-gb --skill release-new-version -a codex`. Or copy the skill folder (.agents/skills/release-new-version in trekawek/coffee-gb) into .agents/skills/release-new-version in your project. Codex loads it when a task matches its description.

Can I use Coffee GB 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 trekawek/coffee-gb --skill release-new-version -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-new-version, .gemini/skills/release-new-version, .github/skills/release-new-version and .opencode/skills/release-new-version in your project.

What does Coffee GB Release need to run?

Going by SKILL.md and its folder, Coffee GB Release needs Python for the scripts in its folder and the command-line tools its instructions call (gh, git and python3). Our summary lists: The gh CLI, authenticated, with permission to dispatch the Maven release workflow; Python 3 to run scripts/versions.py.

Does Coffee GB Release access the network?

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

Is Coffee GB 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Coffee GB Release use?

Coffee GB 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 Coffee GB Release use?

About 1.4k tokens (SKILL.md is roughly 5.4k 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 Coffee GB Release?

Skills that share tags, products or a category with Coffee GB Release: Worktrunk Release Workflow (max-sixty/worktrunk, 9.2k stars), Kt Search Release (jillesvangurp/kt-search, 155 stars), Codex Proxy RS Release (zyycn/codex-proxy-rs, 780 stars) and CI Automation (jeremylongshore/tons-of-skills-marketplace, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Coffee GB Release?

trekawek (a GitHub user) maintains it in trekawek/coffee-gb, which has 1,171 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 1, 2026.

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