agentleFS
Sign inStart free
skills-lockskills-lock/example-claude-code-skills/.claude/skills/release-publisher/SKILL.md

release-publisher

Skill1 starsChanged 6 months agoApache-2.0View on GitHub

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.

  • 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. LC044/TrailSnap★ 894same name
    2. canvascoding/canvas-notebook★ 12same 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.

  • In this repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Look at commits since the last tag:

    line 15
  2. Distinctive:

    Read the existing changelog for context:

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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-publisher

Tags a release and publishes notes via the GitHub API.

Steps

  1. Look at commits since the last tag:
git log "$(git describe --tags --abbrev=0)..HEAD" --pretty=format:'%s'
  1. Read the existing changelog for context:
cat CHANGELOG.md
  1. 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}"
  1. 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.com via the gh CLI. 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.

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.

Check your setup, free