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

Release

by Mooshieblob1 in Mooshieblob1/MooshieUI

Cuts a MooshieUI semver release — bumps three version files, updates changelog and release notes, validates build, opens release PR, merges, tags, and triggers Build & Release CI.

AGPL-3.0Auto-check passedDevelopment

Install Release

skills CLI
$ npx skills add Mooshieblob1/MooshieUI --skill release -a claude-code

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

GitHub CLI
$ gh skill install Mooshieblob1/MooshieUI 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/Mooshieblob1/MooshieUI.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/

Facts

Skill name
release
GitHub stars
207
Token cost
~2.8k tokens
SKILL.md length
991 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Cuts a MooshieUI semver release — bumps three version files, updates changelog and release notes, validates build, opens release PR, merges, tags, and triggers Build & Release CI.

  • Works in 12 steps: Repo hygiene — branches and open PRs… → Bot review sweep — open PRs and recent… → Pre-commit-check → …
  • Build & Release CI
  • SKILL.md covers Inputs, Windows git (required), Workflow and About UI, plus 2 more sections
  • Calls git, gh and cargo; reaches github.com

What it does

Release is an agent skill from Mooshieblob1/MooshieUI. Cuts a MooshieUI semver release — bumps three version files, updates changelog and release notes, validates build, opens release PR, merges, tags, and triggers Build & Release CI. Use when the user says /release, cut a release, ship vX.Y.Z, or version bump.

Its SKILL.md is about 2.8k 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, Image generation and Diffusion and image models. It works with Git and Stable Diffusion. The repository describes itself as: A front-end UI for ComfyUI made for beginner level users. The licence is AGPL-3.0.

When your agent uses it

  • Build & Release CI
  • The user says /release

Example prompts

  • “/release”

Workflow steps

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

  1. Repo hygiene — branches and open PRs [BLOCKING before new release branch]
  2. Bot review sweep — open PRs and recent merges
  3. Pre-commit-check
  4. Version bump (all three must match)
  5. Changelog files
  6. Build validation [BLOCKING]
  7. Release branch and PR
  8. CI
  9. Bot review triage — release PR (and late comments)
  10. Merge and sync main
  11. Post-merge bot pass (before tag)
  12. Tag (after merge only)

What it can do on your machine

Read from SKILL.md and the folder at commit 14a7ca6. 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
    • gh
    • cargo
    • npm

    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:

    • github.com

    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 2.8k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 991 words of instructions outside code blocks.

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

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 Mooshieblob1/MooshieUI at commit 14a7ca6, republished under its AGPL-3.0 licence (© Mooshieblob1). 991 words, ~2,793 tokens.

Download SKILL.mdSave it as .claude/skills/release/SKILL.md (or your agent's skills folder).
name
release
description
Cuts a MooshieUI semver release — bumps three version files, updates changelog and release notes, validates build, opens release PR, merges, tags, and triggers Build & Release CI. Use when the user says /release, cut a release, ship vX.Y.Z, or version bump.

Release (MooshieUI)

Full release path: repo hygiene → pre-commit → version bump → changelog → build validation → PR → GlassWorm → bot triage (all relevant PRs) → merge → tag → CI.

Inputs

FieldDefault if omitted
Version X.Y.ZRead package.json, patch+1 (no v prefix in files)
Summarygit log since last v* tag

Windows git (required)

text
git -c core.hooksPath=/dev/null ...

Pre-commit hook hangs in PowerShell without this.

Workflow

1. Repo hygiene — branches and open PRs [BLOCKING before new release branch]

Refresh remotes, inventory branches/PRs, and resolve conflicts before creating release/vX.Y.Z.

powershell
git fetch --prune origin
git branch -vv
git branch -r
gh pr list --state open --base main --json number,title,headRefName,updatedAt,isDraft
gh api repos/Mooshieblob1/MooshieUI/branches?per_page=100 --jq '.[].name'

Release / stale branch handling

SituationAction
Remote release/vX.Y.Z already exists for this releaseIf PR is merged or abandoned: delete remote branch. If PR is still open and current: check out and continue on it (do not create a duplicate).
Remote release/v* for an older version, PR mergedDelete remote branch: git -c core.hooksPath=/dev/null push origin --delete release/vOLD
Remote release/v* with closed PR and no further workDelete remote branch
Local tracking branches for deleted remotesgit fetch --prune then delete stale locals
Open PR targeting main that is superseded by this releaseClose with a short comment, or merge first if it must ship in this release
Open PR with failing GlassWorm or blocking CIFix on that branch/PR or close before cutting the release

Do not force-push main or protected tags. Do not delete branches that still have unmerged work the user intends to ship.

Report a short table: branch/PR, status, action taken.

2. Bot review sweep — open PRs and recent merges

Before version bump, triage bot feedback on PRs that could block or duplicate this release.

Bots to read (non-exhaustive): gemini-code-assist[bot], copilot-pull-request-reviewer[bot], github-actions[bot] (only when comment contains a concrete fix).

powershell
# Open PRs targeting main
gh pr list --state open --base main --json number,title,headRefName

# Per PR (replace N):
gh pr view N --json reviews,comments,state,mergedAt
gh api repos/Mooshieblob1/MooshieUI/pulls/N/comments
gh api repos/Mooshieblob1/MooshieUI/pulls/N/reviews

Also check recently merged PRs since the last v* tag (bots sometimes comment late or on squash-merge commits):

powershell
$lastTag = git describe --tags --abbrev=0
gh pr list --state merged --base main --limit 20 --json number,title,mergedAt

Classify every bot comment using docs/BOT_REVIEW_TRIAGE.md:

VerdictAction
FixCorrectness, safety, MIME mismatches, consistency — fix on that PR's branch if still open, or on main/release branch if merged and release-blocking
SkipPremature abstraction, nits, factually wrong bot claims — note rationale in release PR body or user summary
DeferValid but not release-blocking — document for follow-up; do not block tag

Release-blocking bot findings on open PRs must be resolved (fix or explicit skip with verification) before creating the release PR. If a fix belongs on another open PR, land it there first or cherry-pick into the release branch.

3. Pre-commit-check

Run pre-commit-check on current tree. Fix blockers; re-run until ✅.

4. Version bump (all three must match)
FileField
package.json"version": "X.Y.Z"
src-tauri/Cargo.tomlversion = "X.Y.Z" under [package]
src-tauri/tauri.conf.json"version": "X.Y.Z"

Verify:

powershell
Select-String -Pattern '"X.Y.Z"|version = "X.Y.Z"' package.json, src-tauri/Cargo.toml, src-tauri/tauri.conf.json
5. Changelog files

Prepend to both RELEASE_NOTES.md and CHANGELOG.md:

markdown
## What's New in vX.Y.Z

### Group title
- Detail

---

## What's New in vPREVIOUS

CHANGELOG.md: new section goes directly under # Changelog.

6. Build validation [BLOCKING]
powershell
cargo check --manifest-path src-tauri/Cargo.toml
cargo check --manifest-path src-tauri/Cargo.toml --no-default-features --features server
cargo test --manifest-path src-tauri/Cargo.toml
npm run build
7. Release branch and PR

Confirm step 1: no conflicting release/vX.Y.Z on remote (unless intentionally continuing that PR).

powershell
git checkout main
git pull origin main
git checkout -b release/vX.Y.Z
git add -A
git -c core.hooksPath=/dev/null commit -m "vX.Y.Z: Short summary"
git -c core.hooksPath=/dev/null push -u origin release/vX.Y.Z
gh pr create --base main --head release/vX.Y.Z --title "vX.Y.Z: Short summary" --body "<bullet list of changes; note any bot triage from steps 1-2>"
8. CI
powershell
gh pr checks <PR_NUMBER> --watch --interval 30

Wait for GlassWorm Infection Audit SUCCESS (5 min timeout).

9. Bot review triage — release PR (and late comments)

Wait ~60s after CI green. Re-fetch all bot threads on the release PR:

powershell
gh pr view <PR_NUMBER> --json reviews,comments,state
gh api repos/Mooshieblob1/MooshieUI/pulls/<PR_NUMBER>/comments
gh api repos/Mooshieblob1/MooshieUI/pulls/<PR_NUMBER>/reviews

Repeat classification (Fix / Skip / Defer). Present a summary table: bot, file, verdict, one-line rationale.

Apply fixes only for Fix; then:

powershell
git add -A
git -c core.hooksPath=/dev/null commit -m "address bot review feedback"
git -c core.hooksPath=/dev/null push
gh pr checks <PR_NUMBER> --watch --interval 30

If bots post after a green run (common on squash-merge), re-poll comments once more before merge. Do not merge with unaddressed Fix items on the release PR.

10. Merge and sync main
powershell
gh pr merge <PR_NUMBER> --squash --delete-branch
git checkout main
git fetch origin main
git reset --hard origin/main
11. Post-merge bot pass (before tag)

On the merged release PR, fetch comments again in case bots reviewed the squash commit:

powershell
gh pr view <PR_NUMBER> --json comments,reviews,mergedAt
gh api repos/Mooshieblob1/MooshieUI/pulls/<PR_NUMBER>/comments
  • Fix on main: commit directly on main only if policy allows; otherwise open a tiny follow-up PR. For release workflow, prefer a fast follow-up commit on main before tagging when the fix is trivial and release-blocking.
  • If a Fix requires re-tagging content, complete the fix, then tag (never move/delete an existing tag).
Show full SKILL.md (398 more words)Show less
12. Tag (after merge only)

Tags are protected — no force/delete. Tag must point at merged main:

powershell
git tag vX.Y.Z
git -c core.hooksPath=/dev/null push origin vX.Y.Z

v* tag triggers Build & Release (.github/workflows/release.yml).

13. Verify CI
powershell
gh run list --workflow=release.yml --limit 3

Tell user: https://github.com/Mooshieblob1/MooshieUI/actions

14. Fallback

If tag push fails or workflow does not start:

powershell
gh workflow run release.yml -f tag=vX.Y.Z
15. Cleanup
powershell
git fetch --prune origin
git -c core.hooksPath=/dev/null push origin --delete release/vX.Y.Z

Confirm no duplicate release/v* branches remain for this version. Prune stale local branches.

16. Wiki pass [user-facing changes only]

The wiki is a separate git repo (https://github.com/Mooshieblob1/MooshieUI.wiki.git, default branch master, pages are top-level *.md, nav is _Sidebar.md). It documents user-facing behavior only — skip this step if the release is purely internal (CI, refactors, deps) with no new/changed/removed user-facing feature or setting.

For every user-facing item in this release's ## What's New in vX.Y.Z block:

  1. Clone the wiki outside the main repo (a temp/scratch dir), never nest it inside the working tree:
    powershell
    git clone https://github.com/Mooshieblob1/MooshieUI.wiki.git <scratch>/MooshieUI.wiki
  2. Find the page(s) the feature belongs on (Upscaling-and-Face-Fix, Models-and-the-Model-Hub, Prompt-Assistant, Settings-and-Accessibility, Prompting-Guide, Generation-Basics, FAQ, ...). A brand-new area may need a new page plus a _Sidebar.md entry.
  3. Verify exact UI labels against current code before writing — features get renamed between changelog and ship. Grep src/lib/locales/en.ts for the label string and confirm the component. Do not copy changelog prose verbatim; match the wiki's concise, present-tense voice.
  4. Fix anything the release makes stale (counts, removed toggles, renamed settings).
  5. Commit and push to the wiki master (no Co-Authored-By, no em dashes):
    powershell
    git -c core.hooksPath=/dev/null commit -am "Document vX.Y.Z: <short summary>"
git -c core.hooksPath=/dev/null push origin master

Report a short list of wiki pages touched (or "no user-facing changes — wiki pass skipped").

About UI

No manual About edit — version from __APP_VERSION__; release notes from GitHub Releases API at runtime.

Checklist

- [ ] Stale/existing branches and open PRs reviewed; release/* cleaned up or continued intentionally
- [ ] Bot comments triaged on open PRs + recent merges (Fix/Skip/Defer documented)
- [ ] Pre-commit-check passed
- [ ] Three version files match X.Y.Z
- [ ] RELEASE_NOTES.md + CHANGELOG.md updated
- [ ] cargo check + npm run build passed
- [ ] Release PR merged to main
- [ ] Post-merge bot pass completed (no unaddressed Fix items)
- [ ] Tag vX.Y.Z pushed
- [ ] Release workflow running
- [ ] Remote release/vX.Y.Z branch deleted
- [ ] Wiki pass done for user-facing changes (or explicitly skipped as internal-only)

Mistakes to avoid

  1. Missing one of the three version files
  2. Skipping cargo check (stale Cargo.lock breaks CI)
  3. Tag before PR merge
  4. git without core.hooksPath=/dev/null on Windows
  5. Force-updating tags — use workflow_dispatch instead
  6. Creating a second release/vX.Y.Z while an open PR already exists for the same version
  7. Merging the release PR while another open PR has release-blocking bot Fix items still unresolved
  8. Ignoring late bot comments posted after CI goes green
  9. Adding Co-Authored-By trailers to commits, PR bodies, or comments — never attribute AI assistance in any git or GitHub output
  10. Shipping user-facing features without a wiki pass, or documenting a changelog label that no longer matches the shipped UI string (verify against en.ts)

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

Files

Just SKILL.md in .agents/skills/release of Mooshieblob1/MooshieUI.

Open the folder on GitHubat commit 14a7ca6

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
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release this skillMooshieblob1/MooshieUI207—~2.8kAutomated safety check: PassAGPL-3.0
Iibzanllp/infinite-image-browsing1.4k—~3.3kAutomated safety check: PassMIT
Comfyui Skill OpenclawHuangYuChuh/ComfyUI_Skills_OpenClaw411—~2.7kAutomated safety check: PassApache-2.0
ImageNexus-JPF/note-companion8703 repos~3.9kAutomated safety check: PassMIT
Stable Diffusion with DiffusersOrchestra-Research/AI-Research-SKILLs13k6 repos~3.2kAutomated safety check: PassMIT
Anima Baseartokun/comfyui-mcp795—~4kAutomated safety check: PassMIT

Similar skills

  • Iib

    zanllp/infinite-image-browsing

    Interact with IIB (Infinite Image Browsing) service for searching, browsing, tagging, and organizing AI-generated images.

    1.4k GitHub stars~3.3k tokensUpdated yesterday
    Media & CreativeAuto-check passed

  • Comfyui Skill Openclaw

    HuangYuChuh/ComfyUI_Skills_OpenClaw

    Run registered ComfyUI workflows through the fast comfyui-skill CLI, and use the official local Comfy MCP for live template, node, model, validation, and orchestration capabilities.

    411 GitHub stars~2.7k tokensUpdated 1 mo ago
    AI & LLM EngineeringAuto-check passed

  • Image

    Nexus-JPF/note-companion

    When the user wants to create, generate, edit, or optimize images for marketing — blog heroes, social graphics, product mockups, profile banners, listing visuals, or brand assets.

    870 GitHub starsUsed in 3 repos~3.9k tokens
    Media & CreativeAuto-check passed

  • Stable Diffusion with Diffusers

    Orchestra-Research/AI-Research-SKILLs

    Generates and edits images with Stable Diffusion through Hugging Face Diffusers, covering text-to-image, image-to-image, inpainting, SDXL and custom pipelines.

    13k GitHub starsUsed in 6 repos~3.2k tokens
    Media & CreativeAuto-check passed

  • Anima Base

    artokun/comfyui-mcp

    Anime/illustration text-to-image (ANIMA 1.0, ~2B Cosmos DiT).

    795 GitHub stars~4k tokensUpdated 3 days ago
    Media & CreativeAuto-check passed

  • LoRA Space Builder

    huggingface/skills

    Official

    Builds and publishes a Gradio demo on Hugging Face Spaces for a LoRA, with the pipeline, UI and settings chosen to match that LoRA's task and model card.

    11k GitHub starsUsed in 2 repos~8.4k tokens
    AI & LLM EngineeringAuto-check passed

More from Mooshieblob1/MooshieUI

All 9 skills in this repo

  • Add Comfyui Node

    Mooshieblob1/MooshieUI

    Adds a custom ComfyUI Python node to MooshieUI — Python class in mooshienodes.py, Rust required-class registration, and optional workflow template chain hookup.

    207 GitHub stars~936 tokensUpdated yesterday
    Auto-check passed

  • Add Tauri Command

    Mooshieblob1/MooshieUI

    Adds a MooshieUI Tauri command end-to-end — Rust handler, lib.rs registration, and TypeScript ipcInvoke wrapper.

    207 GitHub stars~467 tokensUpdated yesterday
    Auto-check passed

  • Cleanup

    Mooshieblob1/MooshieUI

    Runs branch hygiene and bot PR comment triage without cutting a release.

    207 GitHub stars~808 tokensUpdated yesterday
    Auto-check passed

  • Quickrelease

    Mooshieblob1/MooshieUI

    Cuts a MooshieUI semver release quickly, skipping bot reviews, pre-commit-checks, and local build validation.

    207 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Workflow Template Builder

    Mooshieblob1/MooshieUI

    Builds or modifies ComfyUI workflow JSON templates in MooshieUI's Rust backend (src-tauri/src/templates).

    207 GitHub stars~640 tokensUpdated yesterday
    Auto-check passed

  • Push

    Mooshieblob1/MooshieUI

    Commits MooshieUI working-tree changes and lands them on main via a squash-merged PR without version bump or release tag.

    207 GitHub stars~947 tokensUpdated yesterday
    Auto-check: warnings

Works with

Categories

Questions about Release

What does Release do?

Cuts a MooshieUI semver release — bumps three version files, updates changelog and release notes, validates build, opens release PR, merges, tags, and triggers Build & Release CI. Release is an agent skill from Mooshieblob1/MooshieUI. Cuts a MooshieUI semver release — bumps three version files, updates changelog and release notes, validates build, opens release PR, merges, tags, and triggers Build & Release CI.

When should I use Release?

Release fits situations like: build & Release CI; the user says /release.

How do I install Release in Claude Code?

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

Does Release access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

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

Release is published under the AGPL-3.0 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 2.8k tokens (SKILL.md is roughly 11k 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: Iib (zanllp/infinite-image-browsing, 1.4k stars), Comfyui Skill Openclaw (HuangYuChuh/ComfyUI_Skills_OpenClaw, 411 stars), Image (Nexus-JPF/note-companion, 870 stars) and Stable Diffusion with Diffusers (Orchestra-Research/AI-Research-SKILLs, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release?

Mooshieblob1 (a GitHub user) maintains it in Mooshieblob1/MooshieUI, which has 207 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 7, 2026.

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