agentleFS
charliee1wcharliee1w/consolidation-memory/.claude/skills/release/SKILL.md

release

Skill8 starsChanged 9 months agoMITView on GitHub

Evaluate and execute a release with version bump, changelog, tag, and GitHub release

  • Commits and pushes

193 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

  • 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

  • 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

    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

  • parcadeiSkill

    agent-context-isolation

    Agent Context Isolation

    Also in 3 projects that use this

  • +3 more from Grinv

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 183 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If $ARGUMENTS is empty, evaluate whether a release is warranted:

    line 12
  2. Distinctive:

    If warranted, recommend a version number and ask for confirmation

    line 20
  3. Distinctive:

    If not warranted, explain why and stop

    line 21
  4. Distinctive:

    Verify working tree is clean: git status --porcelain

    line 27
  5. Very specific:

    Read current version from pyproject.toml

    line 29
  6. Very specific:

    Read CHANGELOG.md and the commits since last tag

    line 31
  7. Distinctive:

    Write a changelog entry for the new version matching the existing format:

    line 32
  8. Very specific:

    If tests/lint pass, commit: git add pyproject.toml CHANGELOG.md && git commit -m "v$ARGUMENTS"

    line 38
  9. Very specific:

    Create GitHub release: gh release create v$ARGUMENTS --title "v$ARGUMENTS" --notes-from-tag

    line 41
  10. Distinctive:

    If tests or lint fail, stop and report the failures.

    line 43

“Common” is measured: kept by at least 6 in 10 of the 183 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 consolidation-memory

If No Version Argument

If $ARGUMENTS is empty, evaluate whether a release is warranted:

  1. Find the latest git tag: git describe --tags --abbrev=0
  2. List commits since that tag: git log <tag>..HEAD --oneline
  3. Categorize changes (features, fixes, refactors, docs, tests)
  4. Apply release criteria:
    • Release: new features, noteworthy bug fixes, pre-refactor checkpoint
    • Skip: internal refactors only, test-only, docs-only, minor tooling
  5. If warranted, recommend a version number and ask for confirmation
  6. If not warranted, explain why and stop

If Version Provided

Execute release for version $ARGUMENTS:

  1. Verify working tree is clean: git status --porcelain
  2. Pull latest: git pull --ff-only origin main
  3. Read current version from pyproject.toml
  4. Bump version in pyproject.toml to $ARGUMENTS
  5. Read CHANGELOG.md and the commits since last tag
  6. Write a changelog entry for the new version matching the existing format:
    • Date: today's date (YYYY-MM-DD)
    • Sections as appropriate: Features, Bug Fixes, Refactoring, Performance, Security, Documentation, Internal
    • Include test count if it changed
  7. Run tests: python -m pytest tests/ -v
  8. Run linter: python -m ruff check src/ tests/
  9. If tests/lint pass, commit: git add pyproject.toml CHANGELOG.md && git commit -m "v$ARGUMENTS"
  10. Tag: git tag v$ARGUMENTS
  11. Push: git push origin main && git push origin v$ARGUMENTS
  12. Create GitHub release: gh release create v$ARGUMENTS --title "v$ARGUMENTS" --notes-from-tag

If tests or lint fail, stop and report the failures. Do NOT commit broken code.

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.