# Automate GitHub Release Management

Manual releases are error-prone when versioning, testing, deployment, and rollback steps are spread across teams. This skill guides Claude, Codex, and Claude Code through a structured GitHub release workflow with validation checkpoints.

## Install

```bash
npx skillstore add dnyoussef/when-releasing-software-use-github-release-management
```

## Metadata

- Status: approved
- Slug: dnyoussef-when-releasing-software-use-github-release-management
- Skillstore revision: r1
- Version status: missing
- Tree hash: 17ca5072735d00e00992ef245e5d05b697b141b29805861db018fd7257564b3a
- Author: DNYoussef
- GitHub username: DNYoussef
- License: MIT
- Repository: https://github.com/DNYoussef/ai-chrome-extension/tree/main/.claude/skills/github-integration/when-releasing-software-use-github-release-management
- Ref: c579efd02184f1128d6741d16e6c8d951d7d4208
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 69
- Public page: https://skillstore.pages.dev/skills/dnyoussef-when-releasing-software-use-github-release-management
- Manifest: https://skillstore.pages.dev/api/skills/dnyoussef-when-releasing-software-use-github-release-management/manifest

## Capabilities

- Coordinates release, testing, review, CI/CD, and documentation roles for GitHub-hosted projects.
- Guides semantic version selection from commits and existing version files.
- Outlines release branch creation, version updates, artifact builds, and staging validation.
- Provides workflows for standard releases, hotfixes, production rollout, rollback, and post-release monitoring.
- Includes deployment strategy guidance for rolling, blue-green, and canary releases.

## Use Cases

- Coordinate a Standard Release: Plan versioning, staging checks, approvals, deployment, publication, and post-release monitoring in one workflow.
- Prepare an Emergency Hotfix: Guide hotfix branch creation, targeted validation, expedited approval, production deployment, and backporting.
- Improve Release Documentation: Create changelog content, release notes, rollback notes, and stakeholder updates before publication.

## Prompt Templates

### Plan a Release

```
Plan the next GitHub release for my repository. Include version selection, release branch steps, validation gates, and owner assignments.
```

### Create Release Notes

```
Use recent changes to draft release notes. Separate features, fixes, breaking changes, known issues, and upgrade steps.
```

### Validate Staging

```
Review my staging release candidate. Build a validation checklist covering tests, security review, artifacts, monitoring, and rollback readiness.
```

### Coordinate Canary Rollout

```
Coordinate a canary deployment plan for this release. Include traffic stages, health metrics, rollback triggers, communication points, and final publishing steps.
```

## Limitations

- It is guidance only; referenced scripts and templates are not included in the skill package.
- It assumes a GitHub project with existing CI/CD, deployment scripts, and permissions.
- It does not verify cloud infrastructure, secrets, or production readiness by itself.
- Commands can affect production systems and must be reviewed before execution.

## Best Practices

- Review every generated command before running it against shared branches or production.
- Pin external tooling versions and document required permissions before release day.
- Keep rollback criteria, monitoring checks, and stakeholder approvals explicit.

## Anti Patterns

- Running release commands before staging validation and security review are complete.
- Publishing a GitHub release without confirming production health after deployment.
- Using mutable tool tags or missing scripts without verifying their source.

## Security Audit

- Audited at: 2026-07-05T13:37:49.558\+00:00
- Summary: The static Graphviz and Markdown pattern matches are false positives: they are labels, code fences, inline names, or normal local release examples. One medium semantic risk remains because the runbook recommends executing the mutable npx claude-flow@alpha package during release workflows.

## Stats

- Views: 294
- Downloads: 8
- Favorites: 0
- Popularity score: 0