菜单
Write a changeset for the current change. Use when you've edited a publishable packages/* library and need to record a semver bump + consumer-facing release note before the turn ends (the Stop hook enforces this). Reads the diff, picks the bump per affected package, and writes .changeset/*.md.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
| name | changeset |
| description | Write a changeset for the current change. Use when you've edited a publishable packages/* library and need to record a semver bump + consumer-facing release note before the turn ends (the Stop hook enforces this). Reads the diff, picks the bump per affected package, and writes .changeset/*.md. |
You are recording an npm release intent for xNet's published packages
(exploration 0220). A changeset is a small .changeset/<slug>.md file that tells
Changesets how to bump versions and what to write in each package's CHANGELOG.
Only publishable packages need a changeset — i.e. packages/* that are
private: false and NOT in the .changeset/config.json ignore list. Run
node scripts/changeset/publishable-pathspec.mjs to see the exact set. Changes
limited to apps, private/ignored packages, tests, stories, or docs need no
changeset (or an empty one — see below).
Find what changed. Inspect the diff against main:
git diff --stat $(git merge-base HEAD main)...HEAD -- $(node scripts/changeset/publishable-pathspec.mjs)
pnpm turbo run typecheck --affected --dry-run=json # affected package list
Pick the bump per affected package, reading the actual diff — don't just trust the commit prefix:
feat:/fix: when the diff is breaking.Remember the topology: the fixed core (core, crypto, data, react, …)
versions in lockstep — a bump to any one fans across all of them, so you only
need to name one. Periphery packages (cli, trust, slack-compat, …)
version independently.
Write the changeset. Prefer the CLI so the frontmatter is valid:
pnpm changeset # interactive: pick packages + bump, then write the note
Or write .changeset/<short-kebab-slug>.md directly:
---
'@xnetjs/trust': minor
---
Add `requiresCapabilityReprompt()` for re-consent on capability escalation.
The body is consumer-facing: say what changed and why it matters to a package consumer, not how you implemented it.
For non-consumer-visible work (refactors, tooling, docs that still touch a publishable package's source), record an empty changeset so the Stop hook is satisfied and no version is bumped:
pnpm changeset --empty
pnpm changeset:from-commits, run in CI) already maps
conventional-commit prefixes to bumps; your job is to get the bump right from
the diff and write a good note. In CI, scripts/changeset/ai-generate.mjs may
enrich the note and raise (never lower) the bump.scripts/changeset/assert-coverage.mjs) blocks turn-end until
every changed publishable package is covered. CHANGESET_SKIP_HOOK=1 opts out.Read, search, and edit the user's xNet workspace (pages, databases, canvases) via vault files and the xnet CLI.
Write a markdown exploration document for a topic, feature idea, architecture question, or research area. Use when asked to "explore X", "research X", "write an exploration", "investigate X", or "do a deep dive on X". Produces a numbered doc in docs/explorations/ with mermaid diagrams, callouts, collapsible sections, status tables, recommendations, and checklists.
Autonomously implement what was just written — an /explore exploration, a plan, or a spec in the conversation. Use when the user says "implement it", "build it", "ship it", "do it", "make it so", "implement this exploration/plan", or "this looks good, go". Works on a new branch, checks off checklist items and commits as it goes, opens a PR, and merges to main.
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.