Menu
Create a GitHub release with tag after a PR merge — follows the repo's tag and gh release create workflow
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Improve the visual design and UX of the VitePress docs site — layout, colors, typography, components, and responsiveness
Build, preview, and update the VitePress documentation site in docs-site/
Run go test with race detector, analyze failures, fix issues, and re-run until green
Review pull requests against repo standards — Go conventions, test coverage, race detector, CHANGELOG, and docs
Handle upstream-release issues — read changelog deltas, update spec docs, sync protocol and gateway types, run tests, open PR, tag release
| name | release-tag |
| description | Create a GitHub release with tag after a PR merge — follows the repo's tag and gh release create workflow |
| license | MIT |
| metadata | {"audience":"maintainers","workflow":"github"} |
Create a Git tag and GitHub release after a release PR has been merged to main.
Use this skill only after a release PR has been merged to main and all CI checks have passed. Never use this before the PR is merged.
Before proceeding, verify ALL of these:
maingo test ./... -race passes locally on mainCHANGELOG.md has entries under the version being releasedCheckout and pull main:
git checkout main
git pull origin main
Determine version — read from CHANGELOG.md:
## [x.y.z] heading that isn't [Unreleased]v<x.y.z>Verify the tag doesn't exist:
git tag -l "v<x.y.z>"
Build release notes from the CHANGELOG section for this version. Include:
Create the tag and release:
git tag v<x.y.z>
git push origin v<x.y.z>
gh release create v<x.y.z> --title "v<x.y.z>" --notes "<release notes>"
Verify the release:
gh release view v<x.y.z>
Close related issues — if there's an upstream-release issue, close it with a link to the release.
This project uses semantic versioning:
x.y.Z) — bug fixes, test improvements, doc updatesx.Y.0) — new features (new RPC methods, new packages), backward compatibleX.0.0) — breaking changes to exported API (should be rare)v* tags