agentleFS
dimastrianndimastriann/odoo-erp-mcp/.agents/skills/release/SKILL.md

release

Skill3 starsChanged 8 days agoMITView on GitHub

Use when preparing a version bump, release commit, or git tag in this repository. Covers version consistency, CHANGELOG and ROADMAP updates, release builds, and the tag and push checklist.

  • Reads credentials
  • 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

  • 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

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

  • 7

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Check existing tags with git tag --sort=-v:refname.

    line 15
  2. Very specific:

    Update Cargo.lock by building after the version change.

    line 21
  3. Very specific:

    Update CHANGELOG.md using Keep a Changelog sections (Added, Changed, Fixed, Security) and the release date.

    line 22
  4. Very specific:

    Update ROADMAP.md status or commit references only when the roadmap tracks the released work.

    line 24
  5. Very specific:

    Search for stale version strings in README and workflow files: rg -n "0\.[0-9]+\.[0-9]+|v[0-9]+\.[0-9]+\.[0-9]+".

    line 26
  6. Very specific:

    Keep artifact naming in .github/workflows/release.yml derived from the tag.

    line 28
  7. Distinctive:

    Run the full gate, then the release build CI uses:

    line 33
  8. Distinctive:

    Do not add co-author or AI attribution trailers.

    line 49
  9. Distinctive:

    Do not bump versions in unrelated commits.

    line 56
  10. Distinctive:

    Do not rewrite, move, or force-push an existing tag.

    line 57
  11. Distinctive:

    Do not publish a release while the quality gate is failing.

    line 58
  12. Very specific:

    Do not commit .env, config.json, release binaries, or generated artifacts.

    line 59

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

AGENTS.md is the canonical rule set. A release commit is still an atomic commit, but it intentionally groups the version and release metadata changes.

1. Choose the version

  • Follow Semantic Versioning.
  • Confirm the next version with the user when the bump type is not explicit.
  • Check existing tags with git tag --sort=-v:refname.

2. Update every version source

  • Cargo.toml package.version is the runtime source of truth; the MCP serverInfo and /api/version read CARGO_PKG_VERSION.
  • Update Cargo.lock by building after the version change.
  • Update CHANGELOG.md using Keep a Changelog sections (Added, Changed, Fixed, Security) and the release date.
  • Update ROADMAP.md status or commit references only when the roadmap tracks the released work.
  • Search for stale version strings in README and workflow files: rg -n "0\.[0-9]+\.[0-9]+|v[0-9]+\.[0-9]+\.[0-9]+".
  • Keep artifact naming in .github/workflows/release.yml derived from the tag; do not hardcode a new version there.

3. Verify the release

Run the full gate, then the release build CI uses:

cargo fmt --all -- --check
cargo clippy --all-targets --all-features -- -D warnings
cargo test --all-targets --all-features
cargo check --all-targets --all-features
cargo build --all-targets --all-features
cargo build --release --all-targets --all-features

Also run node --test src/views/pagination.test.js when JavaScript changed.

4. Commit and tag

  • Commit with chore(release): prepare vX.Y.Z.
  • Do not add co-author or AI attribution trailers.
  • Tag only after the release commit is on main: git tag vX.Y.Z.
  • Push only when the user asks: git push origin main --tags.
  • Confirm the tag target with git show --stat --oneline vX.Y.Z.

5. Do not

  • Do not bump versions in unrelated commits.
  • Do not rewrite, move, or force-push an existing tag.
  • Do not publish a release while the quality gate is failing.
  • Do not commit .env, config.json, release binaries, or generated artifacts.

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.