Skip to content
Skills Library
Programming · Writing

git-release

/git-release

Draft release notes from merged PRs, propose a semver bump, and emit a copy-pasteable `gh release create` command. Use when preparing a tagged GitHub release.

Licence
MIT
Last repository change
05.07.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 05.07.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Draft release notes from merged PRs, propose a semver bump, and emit a copy-pasteable `gh release create` command. Use when preparing a tagged GitHub release.

Original author description

Draft release notes from merged PRs, propose a semver bump, and emit a copy-pasteable `gh release create` command. Use when preparing a tagged GitHub release.

How it works

  1. What I do
  2. When to use me
  3. What I need from the repo
  4. What I won't do
Original SKILL.md headings · 40 lines, 220 words
SKILL.md preview
---
name: git-release
description: Draft release notes from merged PRs, propose a semver bump, and emit a copy-pasteable `gh release create` command. Use when preparing a tagged GitHub release.
license: MIT
compatibility: opencode
metadata:
  audience: maintainers
  workflow: github
---

## What I do

1. Read recent merged PRs since the last tag and group them:
   - **Features** (`feat:` commits)
   - **Fixes** (`fix:`)
   - **Other** (`refactor:`, `perf:`, `docs:`, `chore:`, …)
2. Propose a **semver bump** based on the diff:
   - Major if any breaking changes (look for `BREAKING CHANGE:` footers or `!:` markers)
   - Minor if any features
   - Patch otherwise
3. Emit a clean **release-notes draft** in Keep-a-Changelog format.
4. Print a ready-to-run command:

```bash
gh release create v<version> --title "<title>" --notes-file release-notes.md
```

## When to use me

When the user is preparing a tagged release. Triggers include:

- "draft release notes"
- "prepare a release"
- "what's in v1.X.Y?"

Ask the user to confirm the proposed version bump before running anything destructive (tag creation, release publish).

## What I need from the repo

- `gh` CLI must be authenticated.
- The repo should have at least one prior tag — if not, propose `v0.1.0`.
- Conventional-commit messages are ideal but not required; without them, I'll group by PR labels or fall back to plain summaries.

## What I won't do

- Push tags or publish releases without explicit confirmation.
- Edit the working tree.
- Generate fictional changelog entries — if a PR is unclear, I quote the original PR title verbatim and flag it for review.

Versions

RepositoryScoreLicence
This page · wesammustafa/opencode-primer100MIT
mgiovani/cc-arsenal100MIT

Database snapshot: 13.11.2026 · package version 6bdc5fae769f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 84release
    Creates a release PR from merged PRs — gathers merged PRs since last tag (plus any unmerged current-branch PR), calculates semver bump from conventional commit titles, generates changelog entries, and opens a release PR. Works from any branch: includes both main and current…
  • 90release-tag
    Cut a release by determining the SemVer bump from history, updating version files across any stack, refreshing the changelog, creating an annotated (optionally signed) Git tag, and pushing the release safely after pre-flight checks. Use when tagging a version, bumping the…
  • 90Release
    This skill should be used when the user asks to "make a release", "create a release", "cut a release", "release a new version", "publish a release", or mentions preparing for release. Provides comprehensive workflow for reviewing changes, updating changelog, determining semver bump, and publishing.
  • 90release-notes
    Write release notes or a CHANGELOG entry from the commits and merged PRs since the last release. Use when asked for "release notes", "update the changelog", "what changed since v1.2", or before tagging a release.
  • 100maintainer-release-notes
    Prepares a release: reads git log since the last tag and the merged pull requests, writes a Keep a Changelog entry and human-friendly release notes, credits every contributor, flags breaking changes and suggests the semver bump. Works with conventional and plain commit messages.…
  • 100chamoji-release
    Cut a release from git history in one command with the chamoji CLI. It picks the semver bump from the commits, adds the CHANGELOG.md section, bumps manifest versions, and makes the release commit and tag (and pushes plus a GitHub release on request). Use it whenever the user…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.