GitHub release management — swarm-orchestrated release pipelines

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://github.com/ruvnet/ruflo/blob/main/.agents/skills/github-release-management/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 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.