agentleFS
niksavisniksavis/basicly/.agents/skills/release-process/SKILL.md

release-process

Skill2 starsChanged 5 days agoMITView on GitHub

Cuts a release with basicly release, pushes it and confirms it published. Use when cutting, tagging or checking a release.

  • Commits and pushes

14 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 1

    Distinctive

    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:

    If either is missing, stop and follow the repository's own release document.

    line 27

“Common” is measured: kept by at least 6 in 10 of the 14 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
<!-- Generated by `basicly skills-build` from skill.yaml. Do not edit; edit the source. -->

Release Process

Cut a release with basicly release, which does every step up to the annotated tag. You choose the version, write the summary and push.

Rules

  • Confirm that this repository releases with basicly release first. The skill ships to every repository that installs basicly, also to one with its own release process.
  • Never do by hand a step that basicly release does. The command checks every precondition before the first write and restores the tree when a later step fails.
  • Write the notes before the cut. The release commit and the tag are one step, so a later commit never reaches the tagged notes.
  • Never clear a refusal by a manual run of the named tool. That records a witness for a check that the gate did not see pass.
  • Never delete a changelog fragment to clear a refusal. A release note must not disappear without notice.
  • The command never pushes. Push only when the user release request includes publication.
  • The user release request authorizes the requested cut and publication. No grant is needed. Required release gates must still pass.

1. Check that the repository uses it

ls changelog.d/ 2>/dev/null; grep -n "## \[Unreleased\]" CHANGELOG.md

If either is missing, stop and follow the repository's own release document.

2. Write the notes

Each change has changelog.d/RECORD-ID.CATEGORY.md. Write a one-paragraph summary under ## [Unreleased], above its first ### heading. The fragment rules are in procedure.

3. Wait for green CI

Cut only from a commit whose CI run on the release branch passed. A red or running build is a stop.

4. Choose the version and run the dry run

uv run basicly release VERSION --issue RECORD-ID --dry-run

You choose major, minor or patch. The dry run writes nothing and lists every refusal at once; refusals gives each fix.

5. Cut the release

uv run basicly release VERSION --issue RECORD-ID

It bumps the version, regenerates projections, rewrites install pins, assembles the changelog, commits and tags. What else it does and the flags are in procedure.

6. Push and confirm

git push origin main
git push origin vX.Y.Z

Confirm that the tag workflow run is green and that the release page matches the summary. When the auto-mode classifier blocks a tag push, read auto-mode.

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.