github-release-management
Github Release Management
Overview
Use this skill to publish GitHub Releases that are accurate, traceable, and operationally usable by consumers.
Scope Boundaries
- Use this skill when the task matches the trigger condition described in
description. - Do not use this skill when the primary task falls outside this skill's domain.
Shared References
- Release note structure guidance:
references/release-note-format.md
Templates And Assets
- Release publication checklist:
assets/github-release-checklist.md
Inputs To Gather
- Version target and release tag/commit mapping.
- Changelog sources (PRs, commits, issues).
- Artifact inventory, integrity policy, and compatibility notes.
- Approval and communication requirements.
Deliverables
- Draft/final GitHub Release package.
- Release notes with upgrade and breaking-change guidance.
- Verified artifact links and integrity evidence.
- Post-release verification record.
Workflow
- Confirm release scope and freeze target commit.
- Generate notes with
scripts/draft_release_notes.py. - Validate notes format and completeness via
references/release-note-format.md. - Verify publication readiness with
assets/github-release-checklist.md. - Publish release and capture verification/follow-up actions.
Scripts
- Generate draft notes from commit range:
python3 scripts/draft_release_notes.py --repo . --version v1.2.3 --from-ref <base_ref> --to-ref HEAD
- Write output file:
python3 scripts/draft_release_notes.py --repo . --version v1.2.3 --from-ref <base_ref> --to-ref HEAD --out /tmp/release-notes.md
Quality Standard
- Release notes reflect shipped changes without ambiguity.
- Version/tag mapping is exact and immutable.
- Breaking changes and migration guidance are explicit.
- Artifacts are available and integrity-verified.
Failure Conditions
- Stop when release scope, version, or tag mapping is inconsistent.
- Stop when artifact integrity cannot be verified.
- Escalate when breaking-change guidance is incomplete for public release.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9