Skip to main content
skill CX Codex

release · nahumlitvin — Claude Code skill for version releases

This skill guides a prismantis release, from version and changelog updates to checks, tagging, and publishing. Use it when preparing a new project version.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add NahumLitvin/prismantis --skill release -a claude-code
Open on GitHub

What release does

The skill lays out the prismantis release sequence: choose a version bump, update both manifests, and build a changelog from merged PRs since the previous tag. It also runs the Codex build; if scripts/package.json changed, it adds the vendor build and checks the bundle contents.

Before publishing, run the verification steps in AGENTS.md, check /prismantis demo and /prismantis demo-rtl, and test a fresh install. The release goes through a PR and a Git tag. A second PR pins the marketplace version; until that change merges, installs continue to use the previous release. The RTL demo requires reading each Hebrew line from right to left.

What it helps with

  • choose a version bump based on the changes
  • build a changelog from PRs since the previous tag
  • refresh generated Codex and vendor files
  • test a fresh plugin install before publishing
  • publish a release through a PR and Git tag

Example prompts for the agent

  • Prepare a prismantis release from the current changes.
  • Choose the version bump and draft the changelog since the previous tag.
  • Run the release checks and prepare the PR and tag.

How to install release

1Skills CLI (Vercel)

npx skills add NahumLitvin/prismantis --skill release -a claude-code

2Manually: put the files in place

~/.claude/skills/release/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/release/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about release

How do I install release in Claude Code?

Run npx skills add NahumLitvin/prismantis --skill release -a claude-code. The skill is available at ~/.claude/skills/release/SKILL.md.

What does the release skill do?

It guides the prismantis release process, including manifest and changelog updates, build checks, the release PR, tagging, and publishing the GitHub release.

What checks are required before a prismantis release?

Run the Verify steps in AGENTS.md, live-check /prismantis demo and /prismantis demo-rtl, then test a fresh install with a throwaway config. Read Hebrew lines in the RTL demo from right to left.

Source text

SKILL.md · MIT
---
name: release
description: Cut a prismantis release - version bump, changelog, verify, tag and push. Use when asked to "release", "bump the version", "ship 0.x" or "publish".
---

# Release

1. **Pick the version.** Breaking option or token renames are minor while below 1.0 (and major after). New features are minor. Fixes are patch.
2. **Set it in both manifests**: `version` in `.claude-plugin/plugin.json` and `plugins[0].version` in `.claude-plugin/marketplace.json`.
3. **Changelog:** add a dated `## [x.y.z]` at the top of docs/CHANGELOG.md, with Added, Changed and Fixed written for users. PRs do not touch the file, so write it from the "What changes for the user" section of every PR merged since the last tag (`git log vPREV..HEAD --oneline`), one entry per user-visible change, linking the PR. Fold in anything still under `## [Unreleased]` and drop that heading.
4. **Generated files:** run `npm --prefix scripts run build:codex`, since PRs leave `codex/` stale. If `scripts/package.json` changed, also run `npm --prefix scripts run build:vendor`, and confirm the bundle has no `import` statements and no non-MIT code (`grep -c -i elk hooks/vendor/*.js` must print 0).
5. **Verify:** run every step in AGENTS.md Verify, plus `live-check` of `/prismantis demo` and `/prismantis demo-rtl`, reading every Hebrew line right to left.
6. **Fresh install test** against a throwaway config:
   ```
   CLAUDE_CONFIG_DIR=<scratch>/fresh claude plugin marketplace add NahumLitvin/prismantis
   CLAUDE_CONFIG_DIR=<scratch>/fresh claude plugin install prismantis@prismantis
   CLAUDE_CONFIG_DIR=<scratch>/fresh claude plugin list
   ```
   Run it after pushing; the marketplace clones from GitHub.
7. **Release PR:** `main` only takes merges through a PR with green checks, so open the release commit as a PR and merge it.
8. **Tag main:** `git tag vX.Y.Z <merge commit> && git push origin vX.Y.Z`. The `release` workflow checks the tag against `plugin.json`, checks the tag is on `main`, and publishes the GitHub release from the CHANGELOG section.
9. **Pin the release:** a second PR sets `ref` to `vX.Y.Z` and `sha` to the tagged commit in the `source` of `.claude-plugin/marketplace.json`, then runs `npm --prefix scripts run build:codex` so `.agents/plugins/marketplace.json`, the Codex copy with a git `url` source, follows. Until it merges, installs keep getting the previous release.
10. **Confirm** CI and the release workflow are green, then run the fresh install test and check `claude plugin list` shows the new version.
11. **Blog:** in `~/git/nahum-writing`, update the "What it draws today" section of `posts/2026-10-02-prismantis/article.md` (version, date, features, counts, limits) and any number in the opening paragraph, then release the blog per its AGENTS.md. Skip when the clone is missing and say so.

© NahumLitvin · MIT · NahumLitvin/prismantis

Similar skills

SKILL.md skills catalog →

release by other authors comes first.

release tobi This skill manages a project release by checking the changelog, installing git hooks, and updating release versions. Use it when the project has a defined release flow. CX Codex +1 2,200installs release Yeachan-Heo A repo-aware skill that discovers release rules from CI files, caches them in .omc/RELEASE_RULE.md, and guides releases. Helpful when preparing tags and version bumps. CX Codex +1 838installs release parcadei Runs a release through five subagents: security audit, E2E tests, final review, version bump, release notes. Useful right before a production deploy. CX Codex +1 481installs release cyrusagents This skill walks a Cyrus CLI release through trusted publishing: prepare, verify, publish, finish. Useful when a version has to ship without touching packages by hand. CX Codex +1 829installs release modelcontextprotocol Walks one milestone release from the release issue through audit, version bumps and the merge PR to the GitHub Release a maintainer publishes. CX Codex +1 ★ 91,595repo stars find-skills vercel-labs Discovers and installs agent skills from skills.sh directly inside your coding assistant. Handy when you need domain-specific workflows for a project. CX Codex +1 4,000,000installs frontend-design official anthropics This skill guides intentional visual design for new interfaces and redesigns. Use it when a generic generated UI is not enough. 1,025,790installs grill-me Matt Pocock grill-me interviews you about a plan or design to expose gaps and sharpen decisions. Use it before implementation starts. 1,424,476installs grill-with-docs Matt Pocock This skill interviews you about a plan or design and creates ADRs and a glossary along the way. Use it when decisions need sharper definition. 1,219,756installs improve-codebase-architecture Matt Pocock This skill scans a codebase for architectural friction, then builds a visual HTML report with refactoring candidates. Use it before a deeper architecture review. 1,163,035installs design-taste-frontend Leonxlnx This skill directs the design of public pages and work screens, then checks the result in a browser through screenshots. Use it when an interface feels generic or unfinished. CX Codex +1 678,700installs

From the same set5

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor