← Search

GitHub release management — swarm-orchestrated release pipelines
DevOps 🧪 Install ran in our test sandbox · Nov 18, 2026 📌 Pinned version: commit 58e0ae7
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: the gh CLI installed and authenticated…

GitHub release management — swarm-orchestrated release pipelines

Plan, version, test, deploy and roll back releases with swarm coordination — changelog generation, semver analysis, multi-target deployment

At a glance
What
Plan, version, test, deploy and roll back releases with swarm coordination — changelog generation, semver analysis, multi-target deployment
Cost
Free
Needs
the gh CLI installed and authenticated, plus claude-flow available (ruv-swarm optional) — releases touch production artifacts, so approval gates stay on
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

GitHub release management — swarm-orchestrated release pipelines is a free Muse skill that orchestrates the full release pipeline with swarm coordination, covering semver analysis with breaking-change detection, changelog generation, automated testing, multi-target deployment to npm, Docker, and GitHub, and rollback management, starting from a draft-first quick start.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit 58e0ae7

Step 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: the gh CLI installed and authenticated, plus claude-flow available (ruv-swarm optional) — releases touch production artifacts, so approval gates stay on Install "GitHub release management — swarm-orchestrated release pipelines" for me. It gives my agent @ruvnet's release orchestration workflow: semver analysis with breaking-change detection from commits, changelog generation, automated testing, multi-target deployment (npm, Docker, GitHub) and rollback management, starting from a draft-first gh release create quick start. MIT-licensed. Repository: https://raw.githubusercontent.com/ruvnet/ruflo/58e0ae7e14e68aab45a4127d6f42f567bbcfb328/.agents/skills/github-release-management/SKILL.md Pinned version: install the code at commit 58e0ae7e14e68aab45a4127d6f42f567bbcfb328 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 (and any helper files) from the repository path 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 "github-release-management". 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. confirm gh is authenticated and approve any release before it publishes; nothing else — it's a workflow guide). 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. If anything looks off, stop and ask me.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 58e0ae7 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 18, 2026
👁 Observed during the install test · Nov 18, 2026 : registry.npmjs.org
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
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
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
58e0ae7 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 18, 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.