agentleFS
alex-voloshin-devalex-voloshin-dev/ai-skills/.agents/skills/release/SKILL.md

release

Skill2 starsChanged 6 months agoMITView on GitHub

Release workflow — version bump, changelog generation, git tag, release notes. Use when preparing a new version for deployment.

  • 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

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 183 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read AGENTS.md at the project root to identify:

    line 14
  2. Distinctive:

    Ask the user (or infer from commits since last release):

    line 22
  3. Distinctive:

    Update version in project files:

    line 54
  4. Very specific:

    Add entry to CHANGELOG.md (create if not exists):

    line 67
  5. Distinctive:

    Create GitHub Release with release notes

    line 127

“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

Structured workflow for preparing a release. Bumps version, generates changelog, creates git tag, and produces release notes.

0. Gather Context

Read AGENTS.md at the project root to identify:

  • Tech stack (determines where version files live: package.json, pom.xml, pyproject.toml, build.gradle)
  • Release conventions (semantic versioning, calver, custom)
  • CI/CD pipeline (what triggers on tag push)
  • Changelog format (CHANGELOG.md, GitHub Releases, both)

1. Determine Release Type

Ask the user (or infer from commits since last release):

  • Major (X.0.0): Breaking changes, removed APIs, major architecture shifts
  • Minor (x.Y.0): New features, non-breaking API additions
  • Patch (x.y.Z): Bug fixes, security patches, dependency updates
// turbo
git describe --tags --abbrev=0 2>/dev/null || echo "No tags found"
// turbo
git log $(git describe --tags --abbrev=0 2>/dev/null || echo "HEAD~20")..HEAD --oneline

2. Analyze Changes

Classify commits since last release:

TypeChangelog Section
feat✨ Features
fix🐛 Bug Fixes
perf⚡ Performance
refactor♻️ Refactoring
docs📚 Documentation
chore/ci🔧 Maintenance
BREAKING CHANGE⚠️ Breaking Changes

3. Bump Version

Update version in project files:

StackFiles to Update
Node.jspackage.json (version field)
Java/Mavenpom.xml (<version>)
Java/Gradlebuild.gradle (version)
Pythonpyproject.toml (version)
.NET*.csproj (<Version>)
GoGit tag only (no version file)

4. Generate Changelog

Add entry to CHANGELOG.md (create if not exists):

## [X.Y.Z] - YYYY-MM-DD

### ⚠️ Breaking Changes
- Description (commit ref)

### ✨ Features
- Description (commit ref)

### 🐛 Bug Fixes
- Description (commit ref)

### ⚡ Performance
- Description (commit ref)

### 🔧 Maintenance
- Description (commit ref)

5. Create Release Commit

Present the changes for user review.

After approval, suggest:

git add -A
git commit -m "chore(release): vX.Y.Z"
git tag -a vX.Y.Z -m "Release vX.Y.Z"

⚠️ Do NOT run git commands without user confirmation. This workflow explicitly overrides the "no git write ops" Hard Rule — git ops are permitted here only after user APPROVE.

6. Release Notes

Generate release notes for GitHub/GitLab:

# Release vX.Y.Z

## Highlights
[1-3 sentence summary of the most important changes]

## What's Changed
[Changelog content from Step 4]

## Upgrade Guide
[If breaking changes — step-by-step migration instructions]

## Contributors
[List contributors from git log]

7. Next Steps

Suggest post-release actions:

  • Push tag: git push origin vX.Y.Z
  • Push branch: git push
  • Create GitHub Release with release notes
  • Deploy to staging: /deploy-staging
  • Deploy to production: /deploy-production
  • Announce release to team

Integration

  • Preceded by: /code-review (all PRs merged)
  • Followed by: /deploy-staging, /deploy-production

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.