Universal Release Workflow
Cut a release on any project type — auto-detected versions, changelogs, GitHub releases, backfill
- What
- Cut a release on any project type — auto-detected versions, changelogs, GitHub releases, backfill
- Cost
- Free
- Needs
- git; the gh CLI (authenticated) if you want GitHub releases created automatically
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a universal release workflow for any project type. Auto-detects the version file (package.json for Node.js, pyproject.toml for Python, Cargo.toml for Rust, marketplace.json for Claude plugins, VERSION/version.txt for generic projects), scans for changelogs (CHANGELOG/HISTORY/CHANGES), generates multi-language changelogs from changes since the last tag, determines the version bump, and creates GitHub releases with annotated tags — including backfilling missing GitHub releases for existing tags from changelog sections, and a `--dry-run` preview mode. Handles optional `.releaserc.yml` hooks and detects whether the origin points to GitHub with an authenticated `gh` CLI. Distinct from the 11 baoyu-* media/content skills already listed (diagram, translate, image-gen, transcripts, infographics…) — this one is dev tooling, not content. Requires git and optionally the `gh` CLI. By @jimliu, listed here with credit to its creator. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Universal Release Workflow is a free Muse skill that cuts a release on any project type, with auto-detected versions, changelogs, GitHub releases and backfill. It auto-detects the version file for Node.js, Python, Rust, Claude plugins or generic projects, scans for changelog entries, and drives the release from detection through publication.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 1567581Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: git; the gh CLI (authenticated) if you want GitHub releases created automatically Install "Universal Release Workflow" for me. Cut a release on any project type — auto-detected versions, changelogs, GitHub releases, backfill Repository: https://raw.githubusercontent.com/jimliu/baoyu-skills/1567581c26ec29f4216c6e6835415bf30343b0e3/.claude/skills/release-skills/SKILL.md Pinned version: install the code at commit 1567581c26ec29f4216c6e6835415bf30343b0e3 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the jimliu-release-skills skill from the repository into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "jimliu-release-skills". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 1567581 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026 · Observed during the install test: registry.npmjs.org
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.