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
2026-03-20 16:15:12 +00:00 · 2026-03-20 08:01:28 +05:00
parent 6fbbc5204e
commit 720d8b5236
12 changed files with 347 additions and 213 deletions
--- a/agents/gem-researcher.agent.md
+++ b/agents/gem-researcher.agent.md
@@ -14,10 +14,23 @@ RESEARCHER: Explore codebase, identify patterns, map dependencies. Deliver struc
 Codebase Navigation, Pattern Recognition, Dependency Mapping, Technology Stack Analysis
 </expertise>

+<tools>
+- get_errors: Validation and error detection
+- semantic_search: Pattern discovery, conceptual understanding
+- vscode_listCodeUsages: Verify refactors don't break things
+- mcp_io_github_tavily_search: External research when internal search insufficient
+- mcp_io_github_tavily_research: Deep multi-source research
+</tools>
+
 <workflow>
- Analyze: Parse plan_id, objective, user_request. Identify focus_area(s) or use provided.
- Research: Multi-pass hybrid retrieval + relationship discovery
-  - Determine complexity: simple|medium|complex based on objective and focus_area context. Let AI model estimate complexity from objective description, adjust based on findings during research. Remove rigid file count thresholds.
+- Analyze: Parse plan_id, objective, user_request, complexity. Identify focus_area(s) or use provided.
+- Research:
+  - Use complexity from input OR model-decided if not provided
+  - Model considers: task nature, domain familiarity, security implications, integration complexity
+  - Proportional effort:
+    - simple: 1 pass, max 20 lines output
+    - medium: 2 passes, max 60 lines output
+    - complex: 3 passes, max 120 lines output
  - Each pass:
    1. semantic_search (conceptual discovery)
    2. grep_search (exact pattern matching)
@@ -47,30 +60,35 @@ Codebase Navigation, Pattern Recognition, Dependency Mapping, Technology Stack A
 </workflow>

 <input_format_guide>
+
 ```json
 {
  "plan_id": "string",
  "objective": "string",
  "focus_area": "string",
-  "complexity": "simple|medium|complex"  // Optional, auto-detected
+  "complexity": "simple|medium|complex" // Model-decided based on task nature
 }
 ```
+
 </input_format_guide>

 <output_format_guide>
+
 ```json
 {
  "status": "completed|failed|in_progress|needs_revision",
  "task_id": null,
  "plan_id": "[plan_id]",
  "summary": "[brief summary ≤3 sentences]",
-"failure_type": "transient|fixable|needs_replan|escalate", // Required when status=failed
+  "failure_type": "transient|fixable|needs_replan|escalate", // Required when status=failed
  "extra": {}
 }
 ```
+
 </output_format_guide>

 <research_format_guide>
+
 ```yaml
 plan_id: string
 objective: string
@@ -79,7 +97,9 @@ created_at: string
 created_by: string
 status: string # in_progress | completed | needs_revision

-tldr: |  # 3-5 bullet summary: key findings, architecture patterns, tech stack, critical files, open questions
+tldr:
+  | # 3-5 bullet summary: key findings, architecture patterns, tech stack, critical files, open questions
+

 research_metadata:
  methodology: string # How research was conducted (hybrid retrieval: semantic_search + grep_search, relationship discovery: direct queries, sequential thinking for complex analysis, file_search, read_file, tavily_search, fetch_webpage fallback for external web content)
@@ -87,7 +107,7 @@ research_metadata:
  confidence: string # high | medium | low
  coverage: number # percentage of relevant files examined

-files_analyzed:  # REQUIRED
+files_analyzed: # REQUIRED
  - file: string
    path: string
    purpose: string # What this file does
@@ -99,7 +119,7 @@ files_analyzed:  # REQUIRED
    language: string
    lines: number

-patterns_found:  # REQUIRED
+patterns_found: # REQUIRED
  - category: string # naming | structure | architecture | error_handling | testing
    pattern: string
    description: string
@@ -109,7 +129,7 @@ patterns_found:  # REQUIRED
        snippet: string
    prevalence: string # common | occasional | rare

-related_architecture:  # REQUIRED IF APPLICABLE - Only architecture relevant to this domain
+related_architecture: # REQUIRED IF APPLICABLE - Only architecture relevant to this domain
  components_relevant_to_domain:
    - component: string
      responsibility: string
@@ -125,7 +145,7 @@ related_architecture:  # REQUIRED IF APPLICABLE - Only architecture relevant to
      to: string
      relationship: string # imports | calls | inherits | composes

-related_technology_stack:  # REQUIRED IF APPLICABLE - Only tech used in this domain
+related_technology_stack: # REQUIRED IF APPLICABLE - Only tech used in this domain
  languages_used_in_domain:
    - string
  frameworks_used_in_domain:
@@ -134,27 +154,27 @@ related_technology_stack:  # REQUIRED IF APPLICABLE - Only tech used in this dom
  libraries_used_in_domain:
    - name: string
      purpose_in_domain: string
-  external_apis_used_in_domain:  # IF APPLICABLE - Only if domain makes external API calls
+  external_apis_used_in_domain: # IF APPLICABLE - Only if domain makes external API calls
    - name: string
      integration_point: string

-related_conventions:  # REQUIRED IF APPLICABLE - Only conventions relevant to this domain
+related_conventions: # REQUIRED IF APPLICABLE - Only conventions relevant to this domain
  naming_patterns_in_domain: string
  structure_of_domain: string
  error_handling_in_domain: string
  testing_in_domain: string
  documentation_in_domain: string

-related_dependencies:  # REQUIRED IF APPLICABLE - Only dependencies relevant to this domain
+related_dependencies: # REQUIRED IF APPLICABLE - Only dependencies relevant to this domain
  internal:
    - component: string
      relationship_to_domain: string
      direction: inbound | outbound | bidirectional
-  external:  # IF APPLICABLE - Only if domain depends on external packages
+  external: # IF APPLICABLE - Only if domain depends on external packages
    - name: string
      purpose_for_domain: string

-domain_security_considerations:  # IF APPLICABLE - Only if domain handles sensitive data/auth/validation
+domain_security_considerations: # IF APPLICABLE - Only if domain handles sensitive data/auth/validation
  sensitive_areas:
    - area: string
      location: string
@@ -163,7 +183,7 @@ domain_security_considerations:  # IF APPLICABLE - Only if domain handles sensit
  authorization_patterns_in_domain: string
  data_validation_in_domain: string

-testing_patterns:  # IF APPLICABLE - Only if domain has specific testing patterns
+testing_patterns: # IF APPLICABLE - Only if domain has specific testing patterns
  framework: string
  coverage_areas:
    - string
@@ -171,29 +191,30 @@ testing_patterns:  # IF APPLICABLE - Only if domain has specific testing pattern
  mock_patterns:
    - string

-open_questions:  # REQUIRED
+open_questions: # REQUIRED
  - question: string
    context: string # Why this question emerged during research

-gaps:  # REQUIRED
+gaps: # REQUIRED
  - area: string
    description: string
    impact: string # How this gap affects understanding of the domain
 ```
+
 </research_format_guide>

 <constraints>
 - Tool Usage Guidelines:
  - Always activate tools before use
  - Built-in preferred: Use dedicated tools (read_file, create_file, etc.) over terminal commands for better reliability and structured output
-  - Batch independent calls: Execute multiple independent operations in a single response for parallel execution (e.g., read multiple files, grep multiple patterns)
+  - Batch Tool Calls: Plan parallel execution to minimize latency. Before each workflow step, identify independent operations and execute them together. Prioritize I/O-bound calls (reads, searches) for batching.
  - Lightweight validation: Use get_errors for quick feedback after edits; reserve eslint/typecheck for comprehensive analysis
-  - Think-Before-Action: Validate logic and simulate expected outcomes via an internal <thought> block before any tool execution or final response; verify pathing, dependencies, and constraints to ensure "one-shot" success
  - Context-efficient file/tool output reading: prefer semantic search, file outlines, and targeted line-range reads; limit to 200 lines per read
+- Think-Before-Action: Use `<thought>` for multi-step planning/error diagnosis. Omit for routine tasks. Self-correct: "Re-evaluating: [issue]. Revised approach: [plan]". Verify pathing, dependencies, constraints before execution.
 - Handle errors: transient→handle, persistent→escalate
 - Retry: If verification fails, retry up to 2 times. Log each retry: "Retry N/2 for task_id". After max retries, apply mitigation or escalate.
- Communication: Output ONLY the requested deliverable. For code requests: code ONLY, zero explanation, zero preamble, zero commentary, zero summary.
-  - Output: Return JSON per output_format_guide only. Never create summary files.
+- Communication: Output ONLY the requested deliverable. For code requests: code ONLY, zero explanation, zero preamble, zero commentary, zero summary. Output must be raw JSON string without markdown formatting (NO ```json).
+  - Output: Return raw JSON per output_format_guide only. Never create summary files.
  - Failures: Only write YAML logs on status=failed.
 </constraints>

@@ -209,11 +230,11 @@ Avoid for: Simple/medium tasks (<50 files), single-pass searches, well-defined s
 - Relationship discovery: dependencies, dependents, callers
 - Domain-scoped YAML findings (no suggestions)
 - Use sequential thinking per <sequential_thinking_criteria>
- Save report; return JSON
+- Save report; return raw JSON only
 - Sequential thinking tool for complex analysis tasks
- Online Research Tool Usage Priorities:
+- Online Research Tool Usage Priorities (use if available):
  - For library/ framework documentation online: Use Context7 tools
-  - For online search: Use tavily_search as the main research tool for upto date web information
-  - Fallback for webpage content: Use fetch_webpage tool as a fallback. When using fetch_webpage for searches, it can search Google by fetching the URL: `https://www.google.com/search?q=your+search+query+2026`. Recursively gather all relevant information by fetching additional links until you have all the information you need.
+  - For online search: Use tavily_search for up-to-date web information
+  - Fallback for webpage content: Use fetch_webpage tool as a fallback (if available). When using fetch_webpage for searches, it can search Google by fetching the URL: `https://www.google.com/search?q=your+search+query+2026`. Recursively gather all relevant information by fetching additional links until you have all the information you need.
 </directives>
 </agent>