Github Release
Use when planning or executing a GitHub release: inspect changes since the last tag, determine SemVer, update a Keep a Changelog entry, run gates, publish tags/assets, and verify rollback and provenance.
Install
npx skills add sandbaseai/workbuddy-skill --skill github-releasegit clone --depth 1 https://github.com/sandbaseai/workbuddy-skill.git /tmp/workbuddy-skill
mkdir -p ~/.claude/skills
cp -r /tmp/workbuddy-skill/skills/github-release ~/.claude/skills/github-releasePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# GitHub Release ## Purpose and boundary Coordinate a reproducible GitHub release from change evidence to published assets. The workflow supports SemVer, Keep a Changelog, tags, release notes, package/asset verification, and rollback evidence. It does not make a release merely because a commit message says “release,” and it must not rewrite history, bypass branch protection, expose credentials, or publish artifacts from an unclean or unverified tree. Use one of two explicit modes: - **PR mode:** create a release branch and PR when repository policy requires review; - **direct mode:** commit/tag/publish on the protected release path only when the caller has already authorized direct automation and branch policy permits it. Do not infer authorization from a request to “prepare” a release. If authority, target branch, version, or publication destination is unknown, produce a plan/report and state the gap. ## Step 1: preflight the repository Verify: ```bash gh auth status gh repo view --json nameWithOwner,defaultBranchRef git status --short --branch git fetch --tags --prune ``` Require a clean worktree, the intended repository, and a known default branch before writing. Record repository, revision, actor, current branch, workflow files, package/build metadata, protected checks, artifact naming, and release workflow behavior. Do not change branches or pull over uncommitted user work without a safe, authorized boundary. ## Step 2: establish the previous release
Details
- Skill name
github-release- Repository
- sandbaseai/workbuddy-skill
- Path
skills/github-release/SKILL.md- License
- MIT
- Repo updated
- 8 September 2026
FAQ
What does the Github Release skill do?
Use when planning or executing a GitHub release: inspect changes since the last tag, determine SemVer, update a Keep a Changelog entry, run gates, publish tags/assets, and verify rollback and provenance.
How do I install the Github Release skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add sandbaseai/workbuddy-skill --skill github-release. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Github Release popular?
It lives in sandbaseai/workbuddy-skill, which has 9 GitHub stars and 3 forks.
Related skills
Access Control Security Best Practices
9sandbaseai/workbuddy-skill
Design, review, implement, and verify least-privilege access controls across users, services, tenants, resources, and administrative workflows.
Accessibility Review
9sandbaseai/workbuddy-skill
Use when reviewing a web interface or interaction for semantic, keyboard, focus, screen-reader, ARIA, and contrast accessibility risks.
Acquire Codebase Knowledge
9sandbaseai/workbuddy-skill
Use when the user asks to map, document, or onboard into an existing codebase and needs evidence-backed architecture, structure, conventions, integrations, testing, and concerns documentation.
Github Research
9sandbaseai/workbuddy-skill
Use when research requires GitHub repositories, source files, specifications, examples, issues, releases, or configuration patterns; choose the right search surface and preserve reproducible source evidence.
Github Actions Hardening
9sandbaseai/workbuddy-skill
Use when reviewing, authoring, auditing, or hardening GitHub Actions workflows for trigger trust, expression injection, token permissions, action supply chain, secrets, outputs, OIDC, and runner exposure.
Merge Conflict Resolution
9sandbaseai/workbuddy-skill
Use when an authorized Git merge, rebase, cherry-pick, or pull operation has conflicts that must be resolved from primary intent and verified before submission.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.