Agent skill

Create Release

Create a concise English release message from commits since the last vX.Y.Z tag, then bump every workspace package to the same version with pnpm changeset and pnpm changeset version.

MITAuto-check passedDevelopment

Install Create Release

skills CLI

$ npx skills add mlightcad/cad-viewer --skill create-release -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install mlightcad/cad-viewer create-release --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/mlightcad/cad-viewer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/create-release .claude/skills/create-release && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "create-release" agent skill from https://github.com/mlightcad/cad-viewer/tree/main/.cursor/skills/create-release into .claude/skills/create-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-release", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/mlightcad/cad-viewer/tree/main/.cursor/skills/create-release

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add mlightcad/cad-viewer --skill create-release -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install mlightcad/cad-viewer create-release --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/mlightcad/cad-viewer.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/create-release .agents/skills/create-release && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "create-release" agent skill from https://github.com/mlightcad/cad-viewer/tree/main/.cursor/skills/create-release into .agents/skills/create-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-release", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add mlightcad/cad-viewer --skill create-release -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install mlightcad/cad-viewer create-release --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/mlightcad/cad-viewer.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/create-release .cursor/skills/create-release && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "create-release" agent skill from https://github.com/mlightcad/cad-viewer/tree/main/.cursor/skills/create-release into .cursor/skills/create-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-release", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/mlightcad/cad-viewer.git --path .cursor/skills/create-release

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add mlightcad/cad-viewer --skill create-release -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install mlightcad/cad-viewer create-release --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/mlightcad/cad-viewer.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/create-release .gemini/skills/create-release && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "create-release" agent skill from https://github.com/mlightcad/cad-viewer/tree/main/.cursor/skills/create-release into .gemini/skills/create-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-release", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install mlightcad/cad-viewer create-release

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add mlightcad/cad-viewer --skill create-release -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/mlightcad/cad-viewer.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/create-release .github/skills/create-release && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "create-release" agent skill from https://github.com/mlightcad/cad-viewer/tree/main/.cursor/skills/create-release into .github/skills/create-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-release", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add mlightcad/cad-viewer --skill create-release -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install mlightcad/cad-viewer create-release --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/mlightcad/cad-viewer.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/create-release .opencode/skills/create-release && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "create-release" agent skill from https://github.com/mlightcad/cad-viewer/tree/main/.cursor/skills/create-release into .opencode/skills/create-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-release", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: create-release
GitHub stars: 1.1k
Token cost: ~1.3k tokens
SKILL.md length: 417 words
Files: 1
Skills in repo: 1
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Create a concise English release message from commits since the last vX.Y.Z tag, then bump every workspace package to the same version with pnpm changeset and pnpm changeset version.

Works in 8 steps: Find last release tag → Collect commits → Draft release message → …
The user asks to release
SKILL.md covers Workflow and Anti-patterns
Calls pnpm and git

What it does

Create Release is an agent skill from mlightcad/cad-viewer. Create a concise English release message from commits since the last vX.Y.Z tag, then bump every workspace package to the same version with pnpm changeset and pnpm changeset version. Use when the user asks to release, cut a release, bump versions, write a release message, or run changesets for this monorepo.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering 3D graphics and WebGL and Monorepo tooling. It works with pnpm and Three.js. The repository describes itself as: The world’s first fully web-based DXF/DWG viewer and editor that runs entirely in the browser — no backend server required. The licence is MIT.

When your agent uses it

The user asks to release
Write a release message
Run changesets for this monorepo

Example prompts

“/create-release”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

Find last release tag
Collect commits
Draft release message
Choose bump type
Create changeset for ALL packages
Version
Verify lockstep versions
Commit / tag

What it can do on your machine

Read from SKILL.md and the folder at commit a39bab9. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- pnpm
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Create Release loads about 1.3k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 417 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~81
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mlightcad/cad-viewer at commit a39bab9, republished under its MIT licence (© mlightcad). 417 words, ~1,251 tokens.

Download SKILL.mdSave it as .claude/skills/create-release/SKILL.md (or your agent's skills folder).

name: create-release
description: Create a concise English release message from commits since the last vX.Y.Z tag, then bump every workspace package to the same version with pnpm changeset and pnpm changeset version. Use when the user asks to release, cut a release, bump versions, write a release message, or run changesets for this monorepo.

Create Release

Keep all packages/* versions identical. Never bump only the packages touched by recent commits.

Workflow

Copy and track:

Release progress:
- [ ] 1. Find last release tag
- [ ] 2. Collect commits since that tag
- [ ] 3. Draft release message (30–100 English words, conventional prefix)
- [ ] 4. Choose bump type (major | minor | patch)
- [ ] 5. Create changeset covering ALL workspace packages
- [ ] 6. Run pnpm changeset version
- [ ] 7. Verify every package version matches
- [ ] 8. Commit version bump (only if user asked to commit)

1. Find last release tag

Use the latest semver vX.Y.Z tag (not by create date alone):

bash

git tag --list "v*.*.*"

Sort by major → minor → patch descending. That tag is the release baseline.

2. Collect commits

bash

git log <latest-tag>..HEAD --pretty=format:"%h %s"

Ignore pure release commits such as release: release X.Y.Z. Summarize the remaining user-facing changes.

3. Draft release message

Requirements:

English only
30–100 words (aim ~40–80)
Start with a conventional prefix: feat:, fix:, perf:, refactor:, docs:, or chore:
One short paragraph summarizing the release theme (not a bullet dump of every commit)
Match existing CHANGELOG tone (see packages/*/CHANGELOG.md)

Prefix choice:

Dominant change is a new capability → feat:
Dominant change is a bug fix → fix:
Mixed with a clear feature theme → prefer feat:
Only tooling/docs → chore: / docs:

Example style (from prior releases):

text

feat: speeds up drawing open with progressive loading by default, a direct-batch convert fast path, and smarter rendering-cache heuristics that share compacted INSERT template geometry. Fonts load on demand during text draw, and picking is fixed so hollow lines are not selected via bbox while hatch islands stay selectable

Show the draft to the user before applying the changeset unless they already approved the wording.

4. Choose bump type

Infer from commits since the last tag (ask if unclear):

Commits indicate	Bump
Breaking API / incompatible change	`major`
New features, no breaking change	`minor`
Fixes / small improvements only	`patch`

Apply the same bump type to every package.

5. Create changeset for ALL packages

Discover packages:

bash

# Every packages/*/package.json that has a "name" field

Include every named workspace package in the changeset frontmatter — public and private. Do not omit untouched packages.

Prefer writing the changeset file directly (agents often lack an interactive TTY for pnpm changeset):

Create .changeset/<short-slug>.md
Frontmatter: each package name → chosen bump type
Body: the approved release message (single paragraph)

---
"@mlightcad/cad-agent-plugin": patch
"@mlightcad/cad-html-plugin": patch
"@mlightcad/cad-pdf-plugin": patch
"@mlightcad/cad-simple-ui-plugin": patch
"@mlightcad/cad-simple-viewer": patch
"@mlightcad/cad-simple-viewer-cli": patch
"@mlightcad/cad-simple-viewer-example": patch
"@mlightcad/cad-diff-viewer": patch
"@mlightcad/cad-diff-viewer-example": patch
"@mlightcad/cad-svg-plugin": patch
"@mlightcad/cad-viewer": patch
"@mlightcad/cad-viewer-example": patch
"@mlightcad/cad-viewer-examples": patch
"@mlightcad/three-renderer": patch
---

feat: your 30–100 word release summary here

Refresh the package list from disk each release; do not hard-code a stale set if packages were added or removed.

If an interactive terminal is available, pnpm changeset is fine only when every package is selected. Skipping packages is a failure.

Show full SKILL.md (119 more words)Show less

6. Version

bash

pnpm changeset version

This consumes the changeset, bumps versions, and updates CHANGELOGs.

7. Verify lockstep versions

Confirm every packages/*/package.json "version" is identical. If any package lagged behind, fix before committing — do not ship divergent versions.

Optional sanity check after edits:

bash

pnpm sync:versions:check

8. Commit / tag

Commit only when the user asks. Suggested message: release: release X.Y.Z (match prior commits).
Creating/pushing the git tag is separate: pnpm release (or pnpm release X.Y.Z). Do not run tag push unless the user asks.

Anti-patterns

Bumping only “affected” packages
Release notes as a raw commit list or over 100 words
Missing conventional prefix on the release message
Running pnpm changeset version with an incomplete changeset
Changing root package.json version (root stays private/1.0.0; only packages/* release together)

Files

Just SKILL.md in .cursor/skills/create-release of mlightcad/cad-viewer.

Open the folder on GitHubat commit a39bab9

Compare with similar skills

Create Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Create Release compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Create Release this skillmlightcad/cad-viewer	1.1k	—	~1.3k	Automated safety check: Pass	MIT	today
Releasecyanfish-x/tellux	207	—	~1.3k	Automated safety check: Pass	MIT	17 days ago
Deploycyanfish-x/tellux	207	—	~1.1k	Automated safety check: Notes	MIT	17 days ago
Link Workspace Packagesnomcopter/react-mosaic	4.8k	6 repos	~760	Automated safety check: Pass	Custom licence	9 days ago
Pnpm Engineteambit/bit	18k	—	~1.9k	Automated safety check: Pass	Custom licence	today
Happy Monorepo Dev Guideslopus/happy	24k	—	~1.8k	Automated safety check: Pass	MIT	today

Similar skills

Release
cyanfish-x/tellux
Cut and publish a new tellux release — bump version, curate a changelog summary from recent commits, pause for the user to manually pnpm publish (browser 2FA), then push the tag and create the…
207 GitHub stars~1.3k tokensUpdated 17 days ago
DevelopmentAuto-check passed
Deploy
cyanfish-x/tellux
Deploy tellux examples/docs sites via project scripts — one local command (pnpm run deploy) rclone-syncs to the self-hosted site then Wrangler Direct Uploads to Cloudflare Pages.
207 GitHub stars~1.1k tokensUpdated 17 days ago
Game DevelopmentAuto-check: notes
Link Workspace Packages
nomcopter/react-mosaic
Link workspace packages in monorepos (npm, yarn, pnpm, bun).
4.8k GitHub starsUsed in 6 repos~760 tokens
DevelopmentAuto-check passed
Pnpm Engine
teambit/bit
Work on the pnpm Rust engine (@pnpm/napi, the pacquet crates) that bit install runs through.
18k GitHub stars~1.9k tokensUpdated today
DevelopmentAuto-check passed
Happy Monorepo Dev Guide
slopus/happy
Local development guide for the Happy pnpm monorepo: install, build, test and run the CLI, server, Expo app and Tauri desktop packages.
24k GitHub stars~1.8k tokensUpdated today
DevelopmentAuto-check passed
Guizang Product Video Skill
op7418/guizang-product-video-skill
制作代码驱动的软件产品宣传片和版本更新片（product promo、release notes video、changelog promo）。从真实功能和产品设计出发定方向，用真实组件、GSAP/Three.js 动效、原创配乐和动作音效完成影片，每支片子的视觉手法都从产品本身推导，不套模板。
702 GitHub stars~1.1k tokensUpdated 7 days ago
DevelopmentAuto-check passed

Works with

Questions about Create Release

What does Create Release do?

Create a concise English release message from commits since the last vX.Y.Z tag, then bump every workspace package to the same version with pnpm changeset and pnpm changeset version. Create Release is an agent skill from mlightcad/cad-viewer.Z tag, then bump every workspace package to the same version with pnpm changeset and pnpm changeset version.

When should I use Create Release?

Create Release fits situations like: the user asks to release; write a release message; run changesets for this monorepo.

How do I install Create Release in Claude Code?

Run `npx skills add mlightcad/cad-viewer --skill create-release -a claude-code`. Or copy the skill folder (.cursor/skills/create-release in mlightcad/cad-viewer) into .claude/skills/create-release in your project. Claude Code loads it when a task matches its description.

How do I install Create Release in Codex?

Run `npx skills add mlightcad/cad-viewer --skill create-release -a codex`. Or copy the skill folder (.cursor/skills/create-release in mlightcad/cad-viewer) into .agents/skills/create-release in your project. Codex loads it when a task matches its description.

Can I use Create Release in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mlightcad/cad-viewer --skill create-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-release, .gemini/skills/create-release, .github/skills/create-release and .opencode/skills/create-release in your project.

What does Create Release need to run?

Going by SKILL.md and its folder, Create Release needs the command-line tools its instructions call (pnpm and git).

Does Create Release access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Create Release safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Create Release use?

Create Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Create Release use?

About 1.3k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Create Release?

Skills that share tags, products or a category with Create Release: Release (cyanfish-x/tellux, 207 stars), Deploy (cyanfish-x/tellux, 207 stars), Link Workspace Packages (nomcopter/react-mosaic, 4.8k stars) and Pnpm Engine (teambit/bit, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Create Release?

mlightcad (a GitHub user) maintains it in mlightcad/cad-viewer, which has 1,119 GitHub stars. The repository was last updated on October 8, 2026.

Source: mlightcad/cad-viewer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Create Release

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Create Release

Workflow

1. Find last release tag

2. Collect commits

3. Draft release message

4. Choose bump type

5. Create changeset for ALL packages

6. Version

7. Verify lockstep versions

8. Commit / tag

Anti-patterns

Files

Compare with similar skills

Similar skills

Release

Deploy

Link Workspace Packages

Pnpm Engine

Happy Monorepo Dev Guide

Guizang Product Video Skill

Related

Questions about Create Release