| 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, then create a GitHub PR with gh pr create. 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 adding or updating Rsbuild end-to-end tests in `e2e/cases`, including new feature coverage, bug reproduction, and regression prevention.
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.
Align Rspress heading anchor IDs between English and Chinese docs. Use for MDX `\{#...}` anchors, shortened hashes, redundant anchors, or dead links.
Use when asked to upgrade `@rspack/core` in this repository to a specific version, run dependency installation and validation, then commit and create a pull request.
Sync uncommitted docs between `website/docs/zh` and `website/docs/en`. Use when authors update docs in one language and need to align the mirrored `.md`/`.mdx` file in the other language.
Improve English documentation under `website/docs/en` by rewriting unnatural translated sentences into clear, professional English while preserving meaning. Use when editing or polishing English docs.