メニュー
Create a coordinated release pull request for the `rstack` and `create-rstack` npm packages. Use when asked to prepare, create, or open an rstack package release PR.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/rstackjs/rstack-cli --skill release-rstackコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Use when migrating projects from standalone Rsbuild, Rslib, Rstest, Rslint, Rspress, Prettier, sort-package-json, lint-staged, husky, or simple-git-hooks tooling to the unified `rstack` package, `rs` commands, and `rstack.config.*`.
Create or update draft GitHub release notes, or output organized Markdown when draft creation is unavailable. Use for release notes, draft releases, release PR checks, npm staged publishing checks, and optional highlights.
Use when asked to create a pull request for this repository. It helps the PR follow the repository's branch safety rules, title convention, pull request template, and concise English writing style.
| name | release-rstack |
| description | Create a coordinated release pull request for the `rstack` and `create-rstack` npm packages. Use when asked to prepare, create, or open an rstack package release PR. |
v, for example 1.2.0.If the version is missing, ask for it before making changes.
create-rstack version:
0.-<identifier>.0; otherwise increment the final prerelease number.create-rstack prerelease suffix.Check the worktree with git status --short. If there are uncommitted changes or untracked files, stop and ask the user how to proceed. Do not stash, discard, or include them.
Confirm the current branch is the repository's default branch. Set the release branch to release/v<version> and check both local and remote branches. If it already exists, stop and ask the user how to proceed.
Create and switch to release/v<version> from the clean default-branch HEAD.
Update the version field in packages/rstack/package.json to <version> and the version field in packages/create-rstack/package.json to the derived create-rstack version.
In every packages/create-rstack/template-*/package.json, set the rstack dependency to ^<version>. Update only that dependency entry and verify every template package manifest uses the same target version.
Run pnpm --filter rstack build:native to regenerate packages/rstack/binding.cjs and packages/rstack/binding.d.cts for the new version. Do not edit generated binding files manually.
Review the diff and confirm it contains only both package version changes, the template rstack dependency updates, and the regenerated binding files above. Verify the two package version changes use the intended matching bump type and no template retains an older rstack version.
Create a commit with this exact message: release: v<version>.
Push the branch to origin. Recheck that the branch being pushed is release/v<version> and never push the default branch directly.
Create a pull request against the default branch. In Codex, use the GitHub connector/plugin; use another available GitHub workflow only when the connector is unavailable. Use release: v<version> as the PR title.
Return the pull request URL.