菜单
Create a Jant release changeset for @jant/core and create-jant using the repository's fixed-version workflow. Use when the user invokes $release by itself, asks to release, prepare a changeset, add a changeset, cut release notes, or run the old Claude release command.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generate a visual proof/demo document for completed Jant work using Showboat and Rodney screenshots. Use when the user invokes $demo by itself, asks for a demo, visual proof, proof document, screenshots showing the current work, or to prove a feature/fix works.
Automate a Jant site over HTTP. Use for creating and updating posts, uploading media, managing collections, editing settings, and running public or authenticated queries against the documented Jant API.
Customize a standalone Jant site created with create-jant. Use for project structure decisions, local development, theme work, deployment setup, settings-driven customization, and deciding whether a change belongs in the site repo or in Jant core.
Operate a standalone Jant site from the command line. Use for local development, deploys, migrations, password resets, site export/import, snapshot recovery, SQL export, and static asset preparation.
| name | release |
| description | Create a Jant release changeset for @jant/core and create-jant using the repository's fixed-version workflow. Use when the user invokes $release by itself, asks to release, prepare a changeset, add a changeset, cut release notes, or run the old Claude release command. |
Create one changeset file for @jant/core and create-jant. Jant uses fixed
versioning, so both packages always release together. This workflow only creates
and commits the changeset file; CI handles version bumps, changelogs, and
publishing.
When invoked with no additional user instructions, treat the invocation as a request to run this workflow now. Start by checking changeset status and summarizing unreleased commits.
Run mise run changeset-status to check for pending changesets.
Summarize unreleased commits with:
git log $(git describe --tags --abbrev=0)..HEAD --oneline
Show the user the unreleased summary and determine the version bump:
patch, minor, or major. Use a bump already supplied by the user; if no
bump is supplied and the user does not answer, default to patch.
Write a concise changelog summary from the commits.
Run the repository task to create the changeset:
mise run changeset-add <bump> "<summary>"
Stage and commit only the new .changeset/*.md file with:
git add .changeset/<new-file>.md
git commit -m "chore: add changeset"
Report the committed changeset and remind the user to create a PR.
mise run version, mise run release, or
mise run release-local.package.json, CHANGELOG.md, or files other than the new
.changeset/*.md file.mise run changeset-add; do not write changeset files by hand.