Release helper
Use when preparing a new tagged release of skil-lock. Inspects recent commits since the last tag, drafts release notes against the conventional-commit prefixes in this repo (feat, fix, build, docs, test, chore), and shows the version bump that GoReleaser will apply. Does not push tags or publish releases — those steps stay manual.From its SKILL.md
npx -y skills add skills-lock/skil-lock --skill release-helperAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 3 stars3 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.
- runs commandsInstructs the agent to run 3 commands, including `git describe --tags --abbrev=0` and 2 more.
SKILL.md
1.9 KB, 368 tokens by cl100k_base, as published. Nobody here has run it
release-helper
Helper for cutting a new tagged release. Surfaces the commits the release would include and drafts notes in the same format the existing GitHub release pages use.
When to use
Invoke this skill from ~/Projects/skil-lock/ (the repository root)
just before tagging a release. The skill is read-only with respect to
the repository; it never modifies tracked files.
What it does
- Find the previous tag:
git describe --tags --abbrev=0
- List the commits since then:
git log "${PREV_TAG}..HEAD" --pretty=format:'%h %s'
-
Group commits by conventional-commit prefix (
feat:,fix:,build:,docs:,test:,chore:) into a draft markdown document. -
Read the existing changelog so the draft slots in cleanly:
cat CHANGELOG.md
- Print the proposed next tag based on the prefixes seen
(
fix:only → patch bump;feat:present → minor bump; anything labeledBREAKING CHANGE:→ major bump).
What it does not do
- Never runs
git tag,git push, orgh release create— those remain manual so a human reviews the draft. - Does not touch the
.goreleaser.ymlfile. - Does not call any external network endpoint.
Constraints for the agent
Run only the commands listed above (git describe, git log,
cat CHANGELOG.md). Do not interpret unrelated arguments; if the user
asks for something outside the scope of preparing a release draft,
ask them to clarify instead of running additional shell commands.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.