agentleFS
skills-lockskills-lock/skil-lock/.claude/skills/release-helper/SKILL.md

release-helper

Skill3 starsChanged 6 months agoApache-2.0View on GitHub

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.

  • Commits and pushes

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. LongNgn204/local-coding-agent★ 56same name
    2. tarikhamilton/claude-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the existing changelog so the draft slots in cleanly:

    line 41
  2. Very specific:

    Never runs git tag, git push, or gh release create — those remain manual so a human reviews the draft.

    line 53
  3. Very specific:

    Does not touch the .goreleaser.yml file.

    line 55
  4. Distinctive:

    Does not call any external network endpoint.

    line 56
  5. Very specific:

    Run only the commands listed above (git describe, git log, cat CHANGELOG.md).

    line 60

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Find the previous tag:
git describe --tags --abbrev=0
  1. List the commits since then:
git log "${PREV_TAG}..HEAD" --pretty=format:'%h %s'
  1. Group commits by conventional-commit prefix (feat:, fix:, build:, docs:, test:, chore:) into a draft markdown document.
  2. Read the existing changelog so the draft slots in cleanly:
cat CHANGELOG.md
  1. Print the proposed next tag based on the prefixes seen (fix: only → patch bump; feat: present → minor bump; anything labeled BREAKING CHANGE: → major bump).

What it does not do

  • Never runs git tag, git push, or gh release create — those remain manual so a human reviews the draft.
  • Does not touch the .goreleaser.yml file.
  • 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.