agentleFS
Sign inStart free
DexForceDexForce/EmbodiChain/.agents/skills/release/SKILL.md

release

Skill240 starsChanged 11 days agoApache-2.0View on GitHub

Use when preparing, drafting, validating, or publishing an EmbodiChain release, including GitHub release notes, version tags, and release artifacts.

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

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

  • 0

    Common

    Most of the 186 edited versions we read keep these.

  • 4

    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:

    Use this skill when the task is about an EmbodiChain release flow:

    line 8
  2. Very specific:

    Use the release workflow in .github/workflows/ as the source of truth for build and publish behavior.

    line 19
  3. Distinctive:

    Keep bullets short and action-oriented.

    line 36
  4. Distinctive:

    Use this exact bullet pattern for release-note items whenever attribution is known:

    line 38
  5. Very specific:

    keep All Commits Since entries attributed the same way

    line 46
  6. Distinctive:

    if a change has no PR number yet, resolve it before drafting the release notes

    line 47
  7. Distinctive:

    When asked to draft a release, produce:

    line 59

“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

Use this skill when the task is about an EmbodiChain release flow:

  • drafting or reviewing GitHub release notes
  • comparing a new release against previous tags
  • checking release artifacts, versioning, or docs publication
  • preparing the tag/release payload for v* releases

Start here

  1. Read references/release-patterns.md.
  2. Identify the target version and the previous released tag.
  3. Use the release workflow in .github/workflows/ as the source of truth for build and publish behavior.

Release note shape

EmbodiChain releases consistently use:

  • a GitHub release title that may be short, e.g. V0.2.2
  • a first body heading like EmbodiChain v0.2.2 Release Notes
  • Highlights
  • Breaking Changes when needed
  • New Features
  • Improvements
  • Bug Fixes
  • Documentation
  • All Commits Since <previous tag> when the release is substantial
  • a short contributor summary

Keep bullets short and action-oriented. Prefer the same wording style used in prior releases: feature-focused, PR-linked, and tied to the author.

Use this exact bullet pattern for release-note items whenever attribution is known:

  • Added emissive light mode to randomize_indirect_lighting by @yuecideng in #274

Format rules:

  • lead with the past-tense change description
  • append by @<author> in #<pr> for each merged PR bullet
  • keep All Commits Since entries attributed the same way
  • if a change has no PR number yet, resolve it before drafting the release notes

What to check

  • version bump is consistent with the previous tag
  • release notes mention dependency upgrades and compatibility breaks explicitly
  • docs changes are included when the release affects navigation, APIs, or public workflows
  • release build artifacts are produced for tagged pushes
  • multi-version docs behavior is preserved for new tags

Output guidance

When asked to draft a release, produce:

  1. the release title
  2. a concise summary paragraph
  3. sectioned bullets in the repo's existing style
  4. any release blockers or verification notes

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