How do I install the Release skill?

Run npx skillmds@latest add fagemx/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?

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

Release by fagemx — Agent Skill

Name: Release
Author: fagemx

Release

Release a new Prismstack version. Runs tests, updates changelog, bumps version, tags, reinstalls globally. Trigger: "release", "ship", "bump version", "new version" Do NOT use when: still making changes (finish first, then release)

fagemx 97f0f3d 2.8 KB Updated Sep 17, 2026

File contents

/release: Ship a New Prismstack Version

You are the release manager. You ensure every release is tested, documented, tagged, and installed.

Phase 1: Pre-Flight Checks

Run tests

bash test/install-test.sh

All tests must pass (expect 67/67). If any fail, stop and report: "Cannot release — N test failures. Fix first."

Check working tree

git status --short

Must be clean (no uncommitted changes). If dirty, stop and report: "Cannot release — uncommitted changes found. Commit or stash first."

Review changes since last release

git describe --tags --abbrev=0 2>/dev/null || echo "no-tags"

Then show commits since that tag:

git log --oneline $(git describe --tags --abbrev=0 2>/dev/null || echo "HEAD~20")..HEAD

Summarize the changes by category: features, fixes, docs, refactors.

Phase 2: Determine Version Bump

Read the current version:

cat VERSION

Read CHANGELOG.md for any unreleased section.

Apply semantic versioning:

breaking: changes → major bump (0.5.0 → 1.0.0)
feat: changes → minor bump (0.5.0 → 0.6.0)
fix: only → patch bump (0.5.0 → 0.5.1)

Present the proposed version and changelog to the user. Ask for confirmation before proceeding:

"Proposed release: vX.Y.Z with these changes: [summary]. Proceed?"

Do NOT continue without user confirmation.

Phase 3: Update Files

VERSION file

Write the new version string (just the number, no v prefix).

CHANGELOG.md

Add a new version header at the top of the changelog (below any title):

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

### Added
- feat: description (from commit messages)

### Fixed
- fix: description

### Changed
- refactor: description

Organize commits under the appropriate heading. Drop trivial commits (typo fixes, etc.) unless they are the only changes.

Phase 4: Commit and Tag

git add VERSION CHANGELOG.md
git commit -m "chore: release vX.Y.Z"
git tag vX.Y.Z

Verify the tag:

git tag --list | tail -5

Phase 5: Reinstall Globally

bash bin/install.sh --global

Verify installation:

ls ~/.claude/skills/prismstack/

Confirm the installed skills match the released version.

Output

Report:

Version: vX.Y.Z
Changes: summary of what shipped
Tests: 67/67 passed
Tag: created
Install: confirmed at ~/.claude/skills/prismstack/

If anything failed, report exactly what and at which phase.

---name: releasedescription: Release a new Prismstack version. Runs tests, updates changelog, bumps version, tags, reinstalls globally. Trigger: "release", "ship", "bump version", "new version" Do NOT use when: still making changes (finish first, then release)---# /release: Ship a New Prismstack VersionYou are the release manager. You ensure every release is tested, documented, tagged, and installed.## Phase 1: Pre-Flight Checks### Run tests```bashbash test/install-test.sh```All tests must pass (expect 67/67). If any fail, stop and report: "Cannot release — N test failures. Fix first."### Check working tree```bashgit status --short```Must be clean (no uncommitted changes). If dirty, stop and report: "Cannot release — uncommitted changes found. Commit or stash first."### Review changes since last release```bashgit describe --tags --abbrev=0 2>/dev/null || echo "no-tags"```Then show commits since that tag:```bashgit log --oneline $(git describe --tags --abbrev=0 2>/dev/null || echo "HEAD~20")..HEAD```Summarize the changes by category: features, fixes, docs, refactors.## Phase 2: Determine Version BumpRead the current version:```bashcat VERSION```Read `CHANGELOG.md` for any unreleased section.Apply semantic versioning:- **breaking:** changes → major bump (0.5.0 → 1.0.0)- **feat:** changes → minor bump (0.5.0 → 0.6.0)- **fix:** only → patch bump (0.5.0 → 0.5.1)Present the proposed version and changelog to the user. Ask for confirmation before proceeding:"Proposed release: vX.Y.Z with these changes: [summary]. Proceed?"Do NOT continue without user confirmation.## Phase 3: Update Files### VERSION fileWrite the new version string (just the number, no `v` prefix).### CHANGELOG.mdAdd a new version header at the top of the changelog (below any title):```markdown## [X.Y.Z] - YYYY-MM-DD### Added- feat: description (from commit messages)### Fixed- fix: description### Changed- refactor: description```Organize commits under the appropriate heading. Drop trivial commits (typo fixes, etc.) unless they are the only changes.## Phase 4: Commit and Tag```bashgit add VERSION CHANGELOG.mdgit commit -m "chore: release vX.Y.Z"git tag vX.Y.Z```Verify the tag:```bashgit tag --list | tail -5```## Phase 5: Reinstall Globally```bashbash bin/install.sh --global```Verify installation:```bashls ~/.claude/skills/prismstack/```Confirm the installed skills match the released version.## OutputReport:1. **Version**: vX.Y.Z2. **Changes**: summary of what shipped3. **Tests**: 67/67 passed4. **Tag**: created5. **Install**: confirmed at `~/.claude/skills/prismstack/`If anything failed, report exactly what and at which phase.

Frequently asked questions