1.6k hyhmrright

release Skill

发布 brooks-lint 新版本:在 package.json 中设置版本号,同步到全部四个插件清单和所有含版本的文本文件(README 徽章、文档站元数据),编写 CHANGELOG 条目,校验后提交、推送、打标签并发布 GitHub Release。触发时机:维护者要求"发布"、"发一个版本"、"上线新版本"或"升版本并发布" brooks-lint。不要触发:仅同步已确定的版本号但不发布(直接用 `npm run bump`)、单独编辑 CHANGELOG,或只是询问发布流程而不要求执行。

安装方式:把技能目录放入 ~/.claude/skills/(Claude Code)或在 claude.ai 设置中启用;也可复制右侧安装命令一键添加。

查看源码

技能指令原文(SKILL.md)

brooks-lint — Release

Target version comes from $ARGUMENTS (e.g. 1.4.0). If empty, ask the maintainer
for the semver bump before doing anything.

Before accepting that version, read the backlog. Run
npm run changelog:audit and look at what is actually unreleased — the bump is decided by the whole range, not by the change
that prompted the release. If the range contains a feature or a new platform and
the maintainer asked for a patch, stop and say so: v1.5.1 was published, then
deleted and re-cut as v1.6.0 because twenty unreleased commits (including a new
platform) had been swept into a patch.

Execute these steps in order. bump-version.mjs reads the version FROM
package.json and does NOT touch the changelog — so the version edit and the
CHANGELOG entry are manual; the script only fans the version out to the manifests
and every version-bearing text file.

  1. Set the source of truth. npm version --no-git-tag-version

(the --no-git-tag-version flag is required — plain npm version would create
its own commit + tag and collide with the manual commit in step 5).

  1. Propagate. npm run bump — writes the version into

.claude-plugin/plugin.json, .claude-plugin/marketplace.json,
.codex-plugin/plugin.json, gemini-extension.json, and every version-bearing
text file discovered by scripts/version-refs.mjs (all six README badges plus
the JSON-LD softwareVersion on the docs landing page). Do not maintain a list
here — the script's is authoritative.

  1. Write the changelog. Add a new section at the top of CHANGELOG.md with

categorized notes (Added / Fixed / Changed) summarizing the commits since the
last release tag. The heading MUST be ## [] - YYYY-MM-DD —
npm run validate parses that exact shape and fails on a bare ## .
3a. Audit the range — every commit, no sampling. Run:

   npm run changelog:audit

It derives the range from the last release tag, applies the only three
exemptions (the release bump, a merge commit whose branch commits are listed
separately, and the star-history refresh — a bot commit touching only the
chart's own two files) and prints the rest as a checklist.
Walk it: each line gets an entry you just wrote, or a reason it needs none.
Nothing else is exempt — internal hardening with no user-visible change
earns an entry, and so does an outside contributor's maintainer-facing fix,
which also earns an @handle credit. A Changelog: trailer on a commit is
surfaced as a flag; that commit's entry is the one you are writing now.

The script exits non-zero on the gap it can prove — a pull request in the
range whose #N the section never cites. That same check runs inside
npm run validate while a release is in progress, so it cannot be skipped,
and validate prints one line whenever it stands down. The rest of the
checklist is judgment and is not enforced. A green audit is not proof of a
complete changelog: a bare #N anywhere in the section clears the gate, a
rebase-merged PR leaves nothing to match, and anything staged into the
release bump itself is never audited. See CLAUDE.md's Release Process.

  1. Validate. npm run validate — fails if any manifest, any version-bearing

text file, or the CHANGELOG entry is out of sync. Fix and re-run until clean.
Then npm test.

  1. Commit & push. Stage everything npm run bump rewrote plus CHANGELOG.md —

read git status rather than naming files, because the version-bearing set is
discovered from disk and is more than one README; commit
with a conventional message (chore(release): bump version to ); push
to main (direct-to-main repo — no PR).

  1. Tag & publish. Create the GitHub release:

gh release create v --title "v" --notes "".

Report the released version and the GitHub release URL when done.

配合站内内容