changeset-management
Use when creating or updating a Changeset for repository work. Enforces the repository's summary-and-bullets format, release bump policy, and no-bump exception.
- License 许可
- MIT
- 所属仓库
- grasdouble/Kitia
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- changeset-management
- description
- Use when creating or updating a Changeset for repository work. Enforces the repository's summary-and-bullets format, release bump policy, and no-bump exception.
03 SKILL.md 正文
Changeset management
Use this skill when a user requests a Changeset or when repository work requires one. Do not use it to edit generated changelogs or package versions.
Determine whether a Changeset is needed
- Identify the current work and whether it changes the published
@grasdouble/kitiapackage. - For user-facing package changes, create a release Changeset with the smallest appropriate bump:
patchfor fixes,minorfor backward-compatible features, ormajorfor breaking changes. - For repository-only work that does not need a package release (CI, tests, contributor skills, or documentation), create an empty no-bump Changeset using
pnpm exec changeset add --emptyand optionally--message "...". - Before creating a file, inspect
.changeset/for a Changeset already associated with this work. Update that file when continuing the same work; do not create one file per iteration. Do not merge unrelated work into an existing Changeset.
Write the repository format
A non-empty Changeset has valid YAML frontmatter naming the package and bump, then one short description followed by grouped detail bullets:
---
"@grasdouble/kitia": minor
---
Short description
- **User-Facing**
- User-visible detail 1
- User-visible detail 2
- **Technical**
- Release-worthy technical detail
Use exactly two spaces before each group label and four spaces before each detail. The User-Facing group MUST come first; keep groups together and omit an empty group. Keep the summary on one unindented line. Do not add ungrouped details, free-standing paragraphs, or blank lines within the grouped details. Write release notes in English unless the user specifies otherwise. Empty-frontmatter no-bump Changesets may carry an optional message and do not use this body format.
Create or update safely
- Preserve facts from the implementation; do not invent behavior or combine unrelated changes.
- Keep the description concise and user-facing. Include only release-worthy behavior in a package Changeset.
- Reuse the existing Changeset for an iteration of the same work. When creating a new one, choose an unused filename under
.changeset/. - When updating a non-empty Changeset, review the entire summary and detail list. Merge duplicate or overlapping information, replace superseded claims, and add only genuinely new details; do not append blindly.
- Do not edit
CHANGELOG.md, package versions, or generated release files manually.
Verify
Run:
pnpm run changeset:format
pnpm changeset status
The first command checks the repository's summary-and-bullets style and permits empty-frontmatter no-bump Changesets. The second validates Changesets metadata, package references, and the computed release plan. For repository-only work, confirm the new entry has empty frontmatter; another Changeset on the branch may independently plan a package release.
04 同仓库更多 Skills
dashboard-demo-maintenance
Maintain Kitia's browser terminal demo at /demo and keep it aligned with the real Ink TUI. Use when updating the demo or changing dashboard screens, keyboard controls, action contracts, resource lifecycle, catalog management, previews, or terminal rendering that can affect it. Preserve the earlier web-style demo at /demo-keep.
changeset-authoring
Create or update Kitia Changesets for user-facing changes, using the repository's concise summary and nested-details format. Use when a change needs a Changeset or when reviewing one.