version-release
Use when the user asks to bump/increment the package version, prepare a release, produce changelog/release notes, or decide whether a change should be called out in the changelog.
- License 许可
- MPL-2.0
- 最近更新
- 2026-11-12
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- version-release
- description
- Use when the user asks to bump/increment the package version, prepare a release, produce changelog/release notes, or decide whether a change should be called out in the changelog.
03 SKILL.md 正文
Version Release
A release-prep skill for coordinating package version bumps and changelog notes.
Repo surfaces
- Package version:
package.jsonand lockfile metadata when present. - Changelog policy:
changelog/about.md. - Current notes:
changelog/unreleased.md. - Cut releases:
changelog/releases/<version>.md.
Modes
Infer the requested mode from the user:
- Changelog note only — add or refine notes in
changelog/unreleased.md; do not change package version. - Version bump only — increment package metadata; do not cut release notes unless requested.
- Release prep — bump version, create release notes, and reset
changelog/unreleased.md.
If the mode or bump type is ambiguous, ask before editing.
Bump rules
Use SemVer language unless the operator gives an exact version:
patch— fixes or polish that do not add a capability.minor— new user-visible capability, command, workflow, or supported surface.major— intentional breaking change for users/operators.- exact version — use exactly what the operator gives.
Prefer npm version <patch|minor|major|version> --no-git-tag-version from the repo root so package.json and lockfiles stay aligned. Do not create git tags, commits, or publish packages unless explicitly asked.
Changelog rules
changelog/unreleased.md is for user-visible notes only. Include things colleagues would notice:
- new or removed npm scripts / CLI commands,
- behavior changes,
- workflow changes,
- renamed or moved supported surfaces,
- release/process changes that affect operators.
Avoid logging purely internal refactors, test-only changes, formatting, or cleanup unless they change how someone uses the project.
Keep sections simple and Keep-a-Changelog-shaped when useful:
# Unreleased
## Added
- ...
## Changed
- ...
## Removed
- ...
Remove empty sections when they add noise, unless preparing a reset stub after a release.
Release prep flow
- Read
package.json,changelog/about.md, andchangelog/unreleased.md. - Confirm the bump type or exact version if the user did not provide one.
- Run
npm version <bump-or-version> --no-git-tag-version. - Read the new version from
package.json. - Create
changelog/releases/<version>.mdwith today's date and release notes copied or summarized fromchangelog/unreleased.md. - Reset
changelog/unreleased.mdto an empty current stub. - Report changed files and suggested validation.
Suggested release file shape:
# <version> - <YYYY-MM-DD>
## Added
- ...
Suggested reset stub:
# Unreleased
No user-visible changes recorded yet.
Safety
- Do not run live Flow/dogfood commands as part of release prep unless explicitly asked.
- If there are existing unrelated working-tree changes, call that out and avoid claiming the release diff is isolated.
- If
npm versionfails or the lockfile cannot be updated cleanly, stop and report the failure instead of hand-editing around it.
04 同仓库更多 Skills
structured-output-repair
暂无简介
ubiquitous-language
Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".
todo-monitor
Create and advance a per-open-item agent todo list using the `npm run todos --` CLI without pausing after each task. Follows todo-contract (strict CLI-only mutation) and todo-enforcer rules.
todo-hard-stop
Execute a per-open-item todo list via the `npm run todos --` CLI under the canonical todo contract, pausing after each completed task for operator feedback.
todo-enforcer
Enforce the per-open-item todo contract (strict CLI-only mutation via `npm run todos --`; no hand-edits to `*.todo.json`) so tracked agent work stays focused, isolated, and linked to an open item.
todo-contract
Defines the canonical per-open-item todo JSON sidecar, strict CLI-only mutation, status vocabulary, and linkage rules.