Automate GitHub Releases with Coordinated Workflows
Manual releases can miss version, validation, artifact, and communication steps. This skill guides release planning, testing, publishing, deployment, monitoring, and rollback with reusable workflows.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "github-release-management" from https://skillstore.io/skills/ruvnet-github-release-management.md and its manifest at https://skillstore.io/api/skills/ruvnet-github-release-management/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "github-release-management". Plan a patch release from version 2.4.0 for three approved fixes.
Expected outcome:
Using "github-release-management". Create release notes for version 3.0.0 with one breaking API change.
Expected outcome:
Using "github-release-management". Review a proposed GitHub Actions release workflow for operational risk.
Expected outcome:
Most alerts are false positives from Markdown fences, quoted substitutions, documentation URLs, and relative links. Six static findings remain for shared temporary files and persisted release credentials. Additional risks include mutable package execution, untrusted metadata entering AI generation, and emergency gate bypasses.
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/ruvnet-github-release-management/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/ruvnet-github-release-management?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/ruvnet-github-release-management?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/ruvnet-github-release-management/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/ruvnet-github-release-management.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>ruvnet. (2026). github-release-management security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/ruvnet-github-release-management/audits/8@techreport{ruvnet-ruvnet-github-release-management-2026,
author = {ruvnet},
title = {github-release-management security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/ruvnet-github-release-management/audits/8},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "github-release-management security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "ruvnet"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/ruvnet-github-release-management/audits/8"
identifiers:
- type: other
value: "skillstore:ruvnet-github-release-management:audit:8"
description: "Skillstore immutable audit report identifier"
Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
ruvnet-github-release-management
2026-09-09
dnyoussef-github-release-management
2026-09-09
A maintainer plans a semantic version, validates changes, drafts notes, publishes artifacts, and completes post-release checks.
A release manager converts existing controls into a staged GitHub workflow with approvals, monitoring, announcements, and rollback criteria.
A DevOps engineer sequences compatible versions across services, validates integrations, and defines an atomic rollback plan.
Plan a patch release for [repository] from [current version]. List prerequisites, validation steps, GitHub release actions, and a rollback checkpoint.
Create release notes for [version] from these approved changes: [changes]. Group features, fixes, breaking changes, upgrade steps, contributors, and known issues.
Design a GitHub Actions workflow for [project]. Include least-privilege permissions, pinned dependencies, tests, artifact signing, approvals, publishing, monitoring, and credential cleanup.
Coordinate releases for [repositories and versions] with [dependencies]. Define sequencing, compatibility gates, staged deployment, observability, failure handling, atomic rollback, and communications.
Author
ruvnetLicense
MIT
Skillstore revision
r2
Version notice
The author did not declare a version.
Ref
ebdfe608f5de2b66ff37ab4af12af8ac4f5e8006
Maintenance freshness
7/25/2026
Usage
8 downloads · 206 views
File structure
📄 SKILL.md
Coordinate Multi-Agent Swarms
Coordinating many agents is hard when roles, topology, and task flow are unclear. This skill provides swarm patterns, hook workflows, and coordination practices for agentic-flow.
Orchestrate Advanced Multi-Agent Swarms
Complex projects need coordinated agents, dependencies, memory, and recovery. This skill provides reusable Claude Flow patterns for research, development, testing, analysis, and monitoring.
Build Adaptive ReasoningBank Agents
AI agents lose useful lessons when outcomes are not recorded. This skill shows how to capture experiences, learn patterns, and recommend better strategies.
Coordinate Advanced Claude Flow Agent Swarms
Complex projects require coordinated agents, durable context, and transparent decisions. This skill guides Claude Flow swarms through queen-led roles, consensus, memory, and sessions.
Structure Software Delivery with SPARC
Complex software work often lacks a consistent path from requirements to completion. This skill applies SPARC phases, specialized modes, and coordinated development workflows.
Build Claude Code Skills
Creating valid Claude or Codex skills can be hard when structure, metadata, and disclosure rules are unclear. This skill provides templates, checklists, and examples for building organized skills.
Automate CI/CD Workflow Design
by sickn33
Manual release work creates delays, missed checks, and inconsistent deployments. This skill helps plan CI/CD workflows with tests, approvals, secrets handling, and rollback notes.
Automate DevOps Pipelines and Deployments
by alirezarezvani
DevOps work often requires repeatable pipeline, infrastructure, and deployment patterns. This skill provides scripts and reference guides for CI/CD, IaC, deployment, and operations review.
Coordinate Cloud DevOps Workflows
by sickn33
Cloud delivery work often spans many tools and phases. This skill organizes infrastructure, CI/CD, Kubernetes, monitoring, security, costs, and recovery work into clear prompts.
Coordinate DevOps Delivery
by Brownbull
DevOps work often spans pipelines, infrastructure, monitoring, and deployment decisions. This skill organizes those tasks into checklists, handoffs, and rollout plans.
Design Safer CI/CD Deployment Pipelines
by wshobson
Teams often ship through pipelines that lack clear gates, rollback plans, or production checks. This skill guides Claude, Codex, and Claude Code to design staged deployment workflows with approvals, strategies, and verification.
Build Terraform Infrastructure Workflows
by sickn33
Terraform delivery involves many connected decisions across resources, state, environments, automation, and security. This skill organizes those decisions into a phased workflow.