Skip to content

refactor: rename gem-chrome-tester to gem-browser-tester#733

Open
mubaidr wants to merge 5 commits intogithub:mainfrom
mubaidr:chrome-to-browser
Open

refactor: rename gem-chrome-tester to gem-browser-tester#733
mubaidr wants to merge 5 commits intogithub:mainfrom
mubaidr:chrome-to-browser

Conversation

@mubaidr
Copy link
Contributor

@mubaidr mubaidr commented Feb 16, 2026

Pull Request Checklist

  • I have read and followed the CONTRIBUTING.md guidelines.
  • My contribution adds a new instruction, prompt, agent, or skill file in the correct directory.
  • The file follows the required naming convention.
  • The content is clearly structured and follows the example format.
  • I have tested my instructions, prompt, agent, or skill with GitHub Copilot.
  • I have run npm start and verified that README.md is up to date.

Description

  • Rename the Chrome-specific testing agent to a browser-agnostic version to support multiple automation tools (Playwright, Chrome DevTools, etc.).
  • Updates all references in orchestrator and planner configurations, and broadens the description and execution workflow to be tool-flexible.
  • Evidence storage rule clarified to apply primarily on failures.

Type of Contribution

  • New instruction file.
  • New prompt file.
  • New agent file.
  • New plugin.
  • New skill file.
  • Update to existing instruction, prompt, agent, plugin, or skill.
  • Other (please specify):

Additional Notes


By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

Rename the Chrome-specific testing agent to a browser-agnostic version
to support multiple automation tools (Playwright, Chrome DevTools, etc.).
Updates all references in orchestrator and planner configurations, and
broadens the description and execution workflow to be tool-flexible.
Evidence storage rule clarified to apply primarily on failures.
Copy link
Contributor

@aaronpowell aaronpowell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got a misspelling and looks like one of the readme's isn't updated correctly.

Remove "detailed thinking on" directive and consolidate operating_rules sections for consistency. Both gem-browser-tester.agent.md and gem-devops.agent.md now share standardized rules: unified tool activation phrasing ("Always activate tools before use"), merged context-efficient reading instructions, and removed agent-specific variations. This simplifies maintenance and ensures consistent behavior across different agent types while preserving core functionality like evidence storage, error handling, and output constraints.
@mubaidr
Copy link
Contributor Author

mubaidr commented Feb 17, 2026

I have fixed the spell issues. Readm issue was probably due to not being on latest code from main. All good now.

@mubaidr mubaidr marked this pull request as draft February 17, 2026 16:49
- Bump plugin version to 1.1.0 in marketplace and plugin.json
- Rename agent from "Chrome Tester" to "Browser Tester" in plugin.json
- Update agent description to focus on browser automation tools instead of Chrome DevTools
- Add symlink for the Browser Tester agent in the plugin's agents directory
@mubaidr mubaidr marked this pull request as ready for review February 17, 2026 17:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants