How do I install the Release skill?

Run npx skillmds@latest add matrixorigin/release in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Release safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Release?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Release free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Release?

matrixorigin (@matrixorigin) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Release by matrixorigin — Agent Skill

Name: Release
Author: matrixorigin

File contents

Flow

Step	Who	How
Bump version, tag, push	You	`make release VERSION=x.y.z`
Build binaries (4 platforms)	CI	`release-rust.yml`
Build + push Docker image	CI	`release-docker.yml`
Create GitHub Release	CI	`softprops/action-gh-release`

Stable Release

git status              # Must be clean
make release VERSION=0.2.0

Does: update Cargo.toml version → cargo check → generate CHANGELOG (git-cliff) → commit → tag → push.

CI then: test → build binaries (x86_64/aarch64 linux/macos) → GitHub Release → Docker image (:0.2.0 + :latest).

Pre-Release

make release-rc VERSION=0.2.0-rc1

Same but: no CHANGELOG, GitHub Release marked prerelease, Docker gets :0.2.0-rc1 (not :latest).

Typical: rc1 → rc2 → stable.

Manual Docker Push

make release-docker                  # :latest
make release-docker VERSION=0.2.0   # :0.2.0 + :latest

CI Workflows

Workflow	Trigger	What
`test.yml`	Push main/develop, PRs	check + clippy + tests
`pr-title.yml`	PR open/edit	Conventional Commits validation
`release-rust.yml`	Tag `v*`	Test → build → GitHub Release
`release-docker.yml`	Tag `v*`	Test → build → Docker Hub

Both release workflows run full test suite before publishing.

Version Locations

memoria/Cargo.toml — source of truth
memoria --version — binary
mcp.json — _version field
Steering rules —

Checklist

Clean working tree, CI green on main
README/docs updated for user-facing changes
Steering rules updated if tool behavior changed
make release VERSION=x.y.z
Verify GitHub Release has 4 binaries + checksums
Verify Docker Hub has new tag

---name: releasedescription: Cut a Memoria release. Version bump, CHANGELOG, CI workflows, Docker image. Use when publishing a new version.---## Flow| Step | Who | How ||------|-----|-----|| Bump version, tag, push | You | `make release VERSION=x.y.z` || Build binaries (4 platforms) | CI | `release-rust.yml` || Build + push Docker image | CI | `release-docker.yml` || Create GitHub Release | CI | `softprops/action-gh-release` |## Stable Release```bashgit status # Must be cleanmake release VERSION=0.2.0```Does: update `Cargo.toml` version → `cargo check` → generate CHANGELOG (git-cliff) → commit → tag → push.CI then: test → build binaries (x86_64/aarch64 linux/macos) → GitHub Release → Docker image (`:0.2.0` + `:latest`).## Pre-Release```bashmake release-rc VERSION=0.2.0-rc1```Same but: no CHANGELOG, GitHub Release marked prerelease, Docker gets `:0.2.0-rc1` (not `:latest`).Typical: `rc1` → `rc2` → stable.## Manual Docker Push```bashmake release-docker # :latestmake release-docker VERSION=0.2.0 # :0.2.0 + :latest```## CI Workflows| Workflow | Trigger | What ||----------|---------|------|| `test.yml` | Push main/develop, PRs | check + clippy + tests || `pr-title.yml` | PR open/edit | Conventional Commits validation || `release-rust.yml` | Tag `v*` | Test → build → GitHub Release || `release-docker.yml` | Tag `v*` | Test → build → Docker Hub |Both release workflows run full test suite before publishing.## Version Locations- `memoria/Cargo.toml` — source of truth- `memoria --version` — binary- `mcp.json` — `_version` field- Steering rules — ``## Checklist- [ ] Clean working tree, CI green on main- [ ] README/docs updated for user-facing changes- [ ] Steering rules updated if tool behavior changed- [ ] `make release VERSION=x.y.z`- [ ] Verify GitHub Release has 4 binaries + checksums- [ ] Verify Docker Hub has new tag

Frequently asked questions

Release