agentleFS
Sign inStart free
pdparchitectpdparchitect/noodle/.agents/skills/mint-release/SKILL.md

mint-release

Skill259 starsChanged 35 days agoApache-2.0View on GitHub

Procedure for minting or publishing a version of Noodle, Computer, Applet, Browser, Hub or the Computer images. Use when the user asks to mint, cut, prepare, release or publish a version, bump a VERSION file, or turn Unreleased changelog notes into a dated release section.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    Do not publish a release unless the user explicitly asks.

    line 8
  2. Distinctive:

    Read it first and follow it.

    line 13
  3. Distinctive:

    Use that changelog entry as the release description.

    line 20
  4. Distinctive:

    Run the affected tests and review the changes.

    line 21
  5. Distinctive:

    Do not create tags manually or reuse published versions.

    line 23

≈ “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

Mint a release

Do not publish a release unless the user explicitly asks. Pushing a new version to main requests publication, so commit and push only on that explicit request.

The complete process, including the per-product version and changelog files, CI behaviour and recovery, is in docs/releases.md. Read it first and follow it; this skill only summarises the preparation.

Prepare

  1. Set the product's version file to an unused, higher X.Y.Z.
  2. Move the relevant Unreleased notes in that product's changelog into ## [X.Y.Z] - YYYY-MM-DD. Keep any remaining work under Unreleased.
  3. Use that changelog entry as the release description.
  4. Run the affected tests and review the changes.

Do not create tags manually or reuse published versions.

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