agentleFS
Sign inStart free
sebyx07sebyx07/ruby2html/.claude/skills/release/SKILL.md

release

Skill23 starsChanged 12 days agoMITView on GitHub

Prepare a ruby2html release PR - bump version, move CHANGELOG Unreleased into a dated section, verify and smoke-test the package, and open a `release: X.Y.Z` PR. Merging that PR publishes (release.yml). Use when the user asks to release, publish, ship or bump the gem version.

196 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-agent-adapter, changelog-style and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    create-agent-adapter

    Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.

    Also in 5 projects that use this

  • GrinvSkill

    changelog-style

    Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.

    Also in 4 projects that use this

  • GrinvSkill

    docs-consistency-check

    Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    component-release

    Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    documentation-consistency

    Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.

    Also in 8 projects that use this

  • rivet-devSkill

    launch-graphics

    Generate agentOS marketing/launch graphics (launch & social heroes, code-snippet cards) from the committed generators in docs-internal/graphics. Use when asked to make, update, or render an agentOS launch image, social image, "agentOS Apps" graphic, or technical code-snippet image.

    Also in 3 projects that use this

  • +3 more from Grinv

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 186 edited versions we read keep these.

  • 0

    Distinctive

    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. Very specific:

    Merge: only on green and only when the user (or, for non-major releases, the developerz.ai maintainer policy) authorizes it.

    line 27
  2. Very specific:

    Never push a v* tag, gem push or run rake release: release.yml owns tagging and publishing.

    line 32
  3. Very specific:

    Never reuse a version number.

    line 33

“Common” is measured: kept by at least 6 in 10 of the 186 edited versions of this file we could read. “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 ruby2html

Follows docs/release.md. Argument: target version X.Y.Z or patch|minor|major.

Merging a change to lib/gem/ruby2html/version.rb into main runs .github/workflows/release.yml, which publishes to RubyGems, then tags and creates the GitHub release. So opening the release PR is safe; merging it is the publish action.

Steps

  1. Preflight (stop and report on any failure): clean tree; branch from up-to-date origin/main; ## [Unreleased] non-empty (else draft entries from git log <last tag>..HEAD and get approval); git tag -l vX.Y.Z and gem list -r ruby2html --all do not contain X.Y.Z. A major needs the owner's explicit go-ahead.
  2. Bump: VERSION = 'X.Y.Z'; CHANGELOG ## [X.Y.Z] - <today> + empty ## [Unreleased] + link reference; bin/changelog-notes X.Y.Z prints the section.
  3. Verify: bundle exec rake compile, CI=1 bundle exec rspec, bundle exec rubocop, bundle exec rake smoke.
  4. PR: branch release/X.Y.Z, one commit release: X.Y.Z, PR titled release: X.Y.Z with the changelog section as the body. Ask before pushing if the user hasn't asked for the PR.
  5. Merge only on green and only when the user (or, for non-major releases, the developerz.ai maintainer policy) authorizes it. Then watch gh run list --workflow release.yml --limit 1.

Never

  • Never push a v* tag, gem push or run rake release: release.yml owns tagging and publishing.
  • Never reuse a version number; never gem yank unless the owner asks.

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