mirror of
https://github.com/github/awesome-copilot.git
synced 2026-03-20 16:15:12 +00:00
gem-team: Add tracing to browser-tester, and improve agent docs and constraints (#1094)
* <think>The user wants me to generate a conventional format commit message based on the git diff output provided. Let me analyze the changes: 1. **`.github/plugin/marketplace.json`**: - Updated the "gem-team" plugin description to include "complexity-aware research, multi-plan selection for critical tasks" - Updated version from "1.2.1" to "1.3.0" 2. **`agents/gem-browser-tester.agent.md`**: - Added `<tools>` section with new tools: get_errors, mcp_io_github_chr_performance_start_trace, mcp_io_github_chr_performance_analyze_insight - Modified the `<expertise>` section (moved closing tag) - Updated `<input_format_guide>` to use proper JSON code block format - Updated `<output_format_guide>` to add "needs_revision" status option and restructured JSON formatting - Updated `<constraints>` section - significantly changed the guidelines This appears to be an update to: - Plugin marketplace version bump - Browser tester agent improvements (new tools, updated workflow constraints, better formatting) Let me generate a conventional commit message: - Type: Could be "feat" for new features or "chore" for maintenance - Scope: could be "marketplace" and "browser-tester" - Message should describe the changes succinctly Looking at the changes more carefully: - Plugin version bump from 1.2.1 to 1.3.0 - this is a feature update - New tools added to browser tester agent - Updated constraints/workflow for browser tester I'll create a commit message that captures the essence: </think> feat: update gem-team to v1.3.0 and enhance browser-tester agent - Bump gem-team plugin version from 1.2.1 to 1.3.0 with updated description - Add performance tracing and insight tools to browser-tester agent - Refactor input/output format guides with proper JSON code blocks - Update agent constraints with improved tool usage and batching guidelines * fix: correct typo "suiteable" to "suitable" in agent documentation
This commit is contained in:
committed by
GitHub
parent
6fbbc5204e
commit
720d8b5236
@@ -41,7 +41,7 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-plugins) for guidelines on how t
|
||||
| [edge-ai-tasks](../plugins/edge-ai-tasks/README.md) | Task Researcher and Task Planner for intermediate to expert users and large codebases - Brought to you by microsoft/edge-ai | 2 items | architecture, planning, research, tasks, implementation |
|
||||
| [flowstudio-power-automate](../plugins/flowstudio-power-automate/README.md) | Complete toolkit for managing Power Automate cloud flows via the FlowStudio MCP server. Includes skills for connecting to the MCP server, debugging failed flow runs, and building/deploying flows from natural language. | 3 items | power-automate, power-platform, flowstudio, mcp, model-context-protocol, cloud-flows, workflow-automation |
|
||||
| [frontend-web-dev](../plugins/frontend-web-dev/README.md) | Essential prompts, instructions, and chat modes for modern frontend web development including React, Angular, Vue, TypeScript, and CSS frameworks. | 4 items | frontend, web, react, typescript, javascript, css, html, angular, vue |
|
||||
| [gem-team](../plugins/gem-team/README.md) | A modular multi-agent team for complex project execution with DAG-based planning, parallel execution, TDD verification, and automated testing with energetic team lead. | 8 items | multi-agent, orchestration, dag-planning, parallel-execution, tdd, verification, automation, security, prd |
|
||||
| [gem-team](../plugins/gem-team/README.md) | A modular multi-agent team for complex project execution with DAG-based planning, complexity-aware research, multi-plan selection for critical tasks, parallel execution, TDD verification, and automated testing. | 8 items | multi-agent, orchestration, dag-planning, parallel-execution, tdd, verification, automation, security, prd |
|
||||
| [go-mcp-development](../plugins/go-mcp-development/README.md) | Complete toolkit for building Model Context Protocol (MCP) servers in Go using the official github.com/modelcontextprotocol/go-sdk. Includes instructions for best practices, a prompt for generating servers, and an expert chat mode for guidance. | 2 items | go, golang, mcp, model-context-protocol, server-development, sdk |
|
||||
| [java-development](../plugins/java-development/README.md) | Comprehensive collection of prompts and instructions for Java development including Spring Boot, Quarkus, testing, documentation, and best practices. | 4 items | java, springboot, quarkus, jpa, junit, javadoc |
|
||||
| [java-mcp-development](../plugins/java-mcp-development/README.md) | Complete toolkit for building Model Context Protocol servers in Java using the official MCP Java SDK with reactive streams and Spring Boot integration. | 2 items | java, mcp, model-context-protocol, server-development, sdk, reactive-streams, spring-boot, reactor |
|
||||
|
||||
Reference in New Issue
Block a user