메뉴
Use when adding or updating Rsbuild end-to-end tests in `e2e/cases`, including new feature coverage, bug reproduction, and regression prevention.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | write-e2e-cases |
| description | Use when adding or updating Rsbuild end-to-end tests in `e2e/cases`, including new feature coverage, bug reproduction, and regression prevention. |
Review uncommitted git changes to define test scope and target behavior.
Read e2e/README.md and follow its conventions.
Prefer @e2e/helper methods (for example dev, build, getDistFiles, findFile, getFileContent, expectFile, and expectFileWithContent) to keep tests minimal, including file and file-content assertions.
Add Playwright cases under e2e/cases, following existing directory patterns.
Use short, direct, and stable assertions. Avoid redundant setup and checks.
Run pnpm e2e to validate.
src directory in every case (required).rsbuild.config.ts to enable easier debugging via npx rsbuild.src code or different Rsbuild configs._node_modules directory and call copyNodeModules() before they are resolved.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.
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.