Release publisher
Skill skills-lock/example-claude-code-skills/.claude/skills/release-publisher
Worked example for skil-lock — pin AI Skill behavior; block unapproved drift in CI.
npx -y skills add skills-lock/example-claude-code-skills --skill release-publisherAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Cut a new git tag, generate release notes from CHANGELOG.md, and publish via the GitHub API. Uses git, gh; calls api.github.com. Use when preparing a tagged release of this repository.
SKILL.md
1.1 KB, as published. Nobody here has run it
release-publisher
Tags a release and publishes notes via the GitHub API.
Steps
- Look at commits since the last tag:
git log "$(git describe --tags --abbrev=0)..HEAD" --pretty=format:'%s'
- Read the existing changelog for context:
cat CHANGELOG.md
- Tag the release (the agent should ask the user to confirm the version bump before running this):
git tag -a "v${NEXT}" -m "release v${NEXT}"
git push origin "v${NEXT}"
- Publish via the GitHub CLI (talks to https://api.github.com):
gh release create "v${NEXT}" --notes-file release-notes.md
Constraints
- Reaches
https://api.github.comvia theghCLI. Does not call any other host. - Pushes a single tag. Does not push commits, branches, or other refs.
- Asks the user to confirm the version bump before tagging or publishing.