Git release
Skill wesammustafa/opencode-primer/.opencode/skills/git-release
Master OpenCode, the open-source AI coding agent — setup, agents, skills, plugins, MCP, Zen & headless CI.
npx -y skills add wesammustafa/opencode-primer --skill git-releaseAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
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.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.6 KB, as published. Nobody here has run it
What I do
- Read recent merged PRs since the last tag and group them:
- Features (
feat:commits) - Fixes (
fix:) - Other (
refactor:,perf:,docs:,chore:, …)
- Features (
- 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
- Major if any breaking changes (look for
- Emit a clean release-notes draft in Keep-a-Changelog format.
- Print a ready-to-run command:
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
ghCLI 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.