メニュー
Use when asked to release `@rsbuild/core` for a specific version.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | release-core |
| description | Use when asked to release `@rsbuild/core` for a specific version. |
1.2.3If the version is missing, ask for it before making changes.
Check the worktree with git status --short. If there are uncommitted edits, stop and ask the user how to proceed.
Update only the version field in these files to the target version:
packages/core/package.jsonpackages/create-rsbuild/package.jsonCreate and switch to branch release/v<version>. If the branch already exists, stop and ask the user how to proceed.
Review the diff and confirm the change is limited to the two version bumps.
Create a commit with this exact message: release: v<version>
Push the branch. If running in Codex, create the PR with the GitHub connector/plugin. Otherwise, use the GitHub workflow available in the current environment. Use the same text for the PR title as the commit message: release: v<version>
If .github/PULL_REQUEST_TEMPLATE.md exists, keep its structure.
Fill it with:
Summary: Release @rsbuild/core and create-rsbuild <version>.Related Links: https://github.com/web-infra-dev/rsbuild/releases/tag/v<version>Use when asked to create a release PR for an official Rsbuild plugin package under `packages/plugin-*`, such as `@rsbuild/plugin-react v2.1.0` or `@rsbuild/plugin-sass v2.0.0`.
Use when profiling, analyzing, reporting, or optimizing Rsbuild performance, including build, dev server, rebuild, static asset serving, memory usage, and CPU profile analysis.
Use when adding or updating Rsbuild end-to-end tests in `e2e/cases`, including new feature coverage, bug reproduction, and regression prevention.
Align Rspress heading anchor IDs between English and Chinese docs. Use for MDX `\{#...}` anchors, shortened hashes, redundant anchors, or dead links.
Create or update draft GitHub releases for the current project's main GitHub repository, then organize GitHub-generated release notes into user-friendly sections without rewriting release note items. Use for preparing, formatting, categorizing, creating, or updating GitHub release notes or draft releases, including optional highlights when the user asks for them.
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.