菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
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 asked to release `@rsbuild/core` for a specific version.
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.
| name | pr-creator |
| description | 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. |
Confirm the current branch with git branch --show-current.
If it is the default branch, create and switch to a new branch before doing anything else.
Use a descriptive branch name, preferably feat-<topic> or fix-<topic>.
Review local changes with git status --short.
Do not revert unrelated user changes.
Before creating the PR, ensure the intended changes are committed and never commit directly on the default branch.
If .github/PULL_REQUEST_TEMPLATE.md exists, read it and follow its structure.
Draft the PR title in the repository's standard format. If the repository uses Conventional Commits, common patterns include:
feat(core): add ...fix(types): ...docs: ...refactor(types): ...chore(deps): ...release: v1.2.0Write the PR body in concise, clear English.
Summary, explain the change context first: the user-facing problem, maintenance goal, or compatibility constraint that makes the change necessary.Test plan or Validation, routine verification commands, generated file lists, or obvious implementation details unless the repository template explicitly requires them or the change has unusual validation risk.This PR adds support for custom logger injection so CLI output can be isolated per instance.This PR fixes incorrect padding in URL labels to keep terminal output aligned across different label lengths.This PR updates the English docs to clarify how the extraction option works and when to enable it.Fill Related Links with issue links, design docs, related PRs, or discussion pages.
If the PR upgrades an npm dependency, add a link to the upgraded version's release notes or tag page when available.
Example: https://github.com/web-infra-dev/rspack/releases/tag/v1.0.0
If there is no relevant link, omit the entire Related Links section from the PR body.
Push the branch only after re-checking the branch name. Never push the default branch directly.
Create the PR with gh pr create.