docs: add write-e2e-cases skill

[chenjiahan]

Summary

Added a new write-e2e-cases skill for creating end-to-end tests.

Checklist

• Tests updated (or not required).
• Documentation updated (or not required).

[gemini-code-assist]

Summary of Changes

Hello @chenjiahan, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the project's testing infrastructure by formalizing the process of writing end-to-end tests. It introduces a dedicated skill that standardizes the approach to E2E test creation, ensuring consistency and clarity across new feature coverage, bug reproductions, and regression prevention. This change aims to streamline the development workflow for tests and improve overall test maintainability.

Highlights

• New E2E Test Writing Skill: A new skill, write-e2e-cases, has been introduced to provide comprehensive guidelines and best practices for creating and updating end-to-end tests within the e2e/cases directory. This skill outlines steps for defining test scope, utilizing helper methods, structuring test cases, and validating tests.
• E2E Documentation Update: The e2e/README.md file has been updated to include a direct reference and link to the newly added write-e2e-cases skill, guiding users on how to leverage this resource for adding new test cases.

Changelog

• .agents/skills/write-e2e-cases/SKILL.md
  • Added a new skill definition file.
  • Included detailed steps for writing E2E tests.
  • Specified the required case structure for E2E tests.
  • Defined constraints regarding source code modifications during testing.
• e2e/README.md
  • Appended a note referencing the new write-e2e-cases skill.
  • Added a markdown link to the SKILL.md file.

Activity

• No specific activity (comments, reviews, or progress updates) has been recorded for this pull request yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a new 'write-e2e-cases' skill, providing clear documentation for creating end-to-end tests. The changes are well-structured, and a link to the new skill has been added to the E2E README. I have one minor suggestion to improve the formatting in the new skill file for better readability.

[Copilot]

Pull request overview

Adds documentation for a new local agent skill (write-e2e-cases) to guide contributors when creating or updating Rsbuild end-to-end (Playwright) tests.

Changes:

• Document a new local skill for writing/updating E2E test cases.
• Link the E2E README to the new skill documentation for discoverability.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
e2e/README.md	Adds a reference link to the new write-e2e-cases local skill for adding E2E cases.
.agents/skills/write-e2e-cases/SKILL.md	Introduces the new skill with steps, case structure guidance, and constraints for adding E2E tests.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.