SkillsAdd

netresearch/github-release-skill · Archived

github-release

Use when creating releases, version bumps, tagging, release health checks, or when user says 'release', 'tag', 'version bump'. Also activates on gh release commands to BLOCK them and redirect to safe process.

First seen Apr 21, 2026

Installation

$ npx skills add netresearch/github-release-skill --skill github-release
View on skills.sh ↗ GitHub repository ↗

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

github-issues Similar · more installs
github/awesome-copilot

Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to cre…

15.5K installs
create-github-action-workflow-specification Similar · more installs
github/awesome-copilot

Create a formal specification for an existing GitHub Actions CI/CD workflow, optimized for AI c…

10.5K installs
create-github-issues-feature-from-implementation-plan Similar · more installs
github/awesome-copilot

Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request…

9.3K installs
create-github-pull-request-from-specification Similar · more installs
github/awesome-copilot 9K installs

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

analyzing-release-readiness Similar name
aws/agent-toolkit-for-aws

Trigger a pre-merge release readiness review on a GitHub PR, GitLab MR, or local branch. Use wh…

1.1K installs
running-release-tests Similar name
aws/agent-toolkit-for-aws

Run automated release testing (UI or API) via the AWS DevOps Agent using a pre-configured test …

1.1K installs
sentry-setup-releases Similar name
getsentry/sentry-for-ai

Set up Sentry releases and deploy tracking — tag events with a version and environment, create …

32 installs
write-release-notes Similar name
tldraw/tldraw

Writing release notes articles for tldraw SDK releases. Use when creating new release documenta…

323 installs
update-release-notes Similar name
tldraw/tldraw

Update the release notes file at `apps/docs/content/releases/next.mdx` in the tldraw/tldraw rep…

107 installs
release-skills Similar name
jimliu/baoyu-skills

Universal release workflow. Auto-detects version files and changelogs. Supports Node.js, Python…

24.4K installs
More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 3
License LICENSE-CC-BY-SA-4.0
Default branch main
Open issues 1
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Version0.12.0
License(MIT AND CC-BY-SA-4.0). See LICENSE-MIT and LICENSE-CC-BY-SA-4.0
CompatibilityRequires gh CLI, git with GPG/SSH signing configured.
Allowed toolsBash(gh:*) Bash(git:*) Read Write Edit Glob Grep
More metadata
author
Netresearch DTT GmbH
version
0.12.0
repository
https://github.com/netresearch/github-release-skill

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,892 B
  • docs SUMMARY.md 230 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 16 installs

SKILL.md

GitHub Release Skill

Critical Rules

NEVER run gh release create or gh release delete.

Blocked by hooks. Immutable releases (GA Oct 2025) make tag names permanent — a lightweight tag from gh release create burns that name forever, unrecoverably. CI creates releases from signed tags.

gh release edit is allowed ONLY for --notes / --notes-file to overhaul the release description after CI publishes. All other gh release edit flags are blocked.

No editorializing in release notes, PR/commit text and docs — state what a release does, not how good the work is; no self-praise or narrating the expected. See references/no-editorializing.md.

Start Here

scripts/release-status.sh -R owner/repo reports the phase and a computed NEXT, exiting 0 only when finished. scripts/release-notes-status.sh checks the published body.

Release Flow

  1. Detect ecosystem — find the project type's version files (see references/ecosystem-detection.md)
  2. Determine next version — from conventional commits or user input (major/minor/patch)
  3. Bump version files — every ecosystem-specific one, consistently
  4. Update CHANGELOG.md — add a release section with date and changes
  5. Create release branch and PR — release/vX.Y.Z, always via PR (branch protection typically blocks direct pushes)
  6. After PR merge — git checkout main && git pull, assert HEAD equals the remote tip (stale-worktree guard), then tag main's HEAD, never the release/vX.Y.Z tip: git tag -s vX.Y.Z -m "vX.Y.Z" — see references/release-process.md Phase 3.
  7. Push tag — git push origin vX.Y.Z triggers CI
  8. CI publishes release — artifacts, checksums, auto-generated notes
  9. Overhaul release description — rewrite CI's notes into a narrative; @mention every contributor and reporter inline at their change, never as a ## Contributors section. Source them from scripts/harvest-contributors.sh, never git log. Verify with scripts/release-notes-status.sh. See references/release-process.md Phase 5.
  10. Do NOT re-run the release workflow after step 9 — many regenerate the body each run, overwriting the overhaul. For downstream retries, use a dispatcher — see references/ter-republish.md.

Commands

  • /release — full release flow (detect, bump, PR, tag)
  • /release-prepare — bump versions and open PR only (no tag)
  • /release-status — check release health (version drift, unsigned tags, missing workflows)

Delegation

  • Supply chain security (SLSA, SBOMs, attestations): delegate to enterprise-readiness skill
  • Branch strategy and conventional commits: delegate to git-workflow skill

References

  • references/release-process.md
  • references/ecosystem-detection.md — version-file patterns
  • references/immutable-releases.md — immutable releases, tag burning
  • references/supply-chain-security.md — SLSA, Sigstore
  • references/recovery-procedures.md — burned tags, stuck drafts, drift, body clobbering
  • references/ter-republish.md — TER re-publish
  • references/typo3-ter-publishing.md — TYPO3 TER publish gotchas
  • references/ci-workflow-templates.md — CI workflow templates
  • references/no-editorializing.md — no self-praise