Awesome/awesome-copilot
1
0
Fork 0
mirror of https://github.com/github/awesome-copilot.git synced 2026-04-13 03:35:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

Release 1.3.4: Documentation Refinements, Agent Updates, and Retry Enhancement (#1160)

Browse Source 
* feat(orchestrator): add Discuss Phase and PRD creation workflow

- Introduce Discuss Phase for medium/complex objectives, generating context‑aware options and logging architectural decisions
- Add PRD creation step after discussion, storing the PRD in docs/prd.yaml
- Refactor Phase 1 to pass task clarifications to researchers
- Update Phase 2 planning to include multi‑plan selection for complex tasks and verification with gem‑reviewer
- Enhance Phase 3 execution loop with wave integration checks and conflict filtering

* feat(gem-team): bump version to 1.3.3 and refine description with Discuss Phase and PRD compliance verification

* chore(release): bump marketplace version to 1.3.4

- Update `marketplace.json` version from `1.3.3` to `1.3.4`.
- Refine `gem-browser-tester.agent.md`:
  - Replace "UUIDs" typo with correct spelling.
  - Adjust wording and formatting for clarity.
  - Update JSON code fences to use ````jsonc````.
  - Modify workflow description to reference `AGENTS.md` when present.
- Refine `gem-devops.agent.md`:
  - Align expertise list formatting.
  - Standardize tool list syntax with back‑ticks.
  - Minor wording improvements.
- Increase retry attempts in `gem-browser-tester.agent.md` from 2 to 3 attempts.
- Minor typographical and formatting corrections across agent documentation.

* refactor: rename prd_path to project_prd_path in agent configurations

- Updated gem-orchestrator.agent.md to use `project_prd_path` instead of `prd_path` in task definitions and delegation logic.
- Updated gem-planner.agent.md to reference `project_prd_path` and clarify PRD reading.
- Updated gem-researcher.agent.md to use `project_prd_path` and adjust PRD consumption logic.
- Applied minor wording improvements and consistency fixes across the orchestrator, planner, and researcher documentation.
This commit is contained in:
Muhammad Ubaid Raza
2026-03-25 03:57:19 +05:00
committed by GitHub
parent 7e326fe334
commit 7471eb5492
10 changed files with 178 additions and 178 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
agents/gem-browser-tester.agent.md
View File

@@ -16,17 +16,16 @@ Browser Automation (Chrome DevTools MCP, Playwright, Agent Browser), E2E Testing
<tools>
- get_errors: Validation and error detection
- mcp_io_github_chr_performance_start_trace: Performance tracing, Core Web Vitals
- mcp_io_github_chr_performance_analyze_insight: Performance insight analysis
</tools>
<workflow>
- READ GLOBAL RULES: If `AGENTS.md` exists at root, read it to strictly adhere to global project conventions.
- Initialize: Identify plan_id, task_def, scenarios.
- Execute: Run scenarios. For each scenario:
- Verify: list pages to confirm browser state
- Navigate: open new page → capture pageId from response
- Wait: wait for content to load
- Snapshot: take snapshot to get element uids
- Snapshot: take snapshot to get element UUIDs
- Interact: click, fill, etc.
- Verify: Validate outcomes against expected results
- On element not found: Retry with fresh snapshot before failing
@@ -41,7 +40,7 @@ Browser Automation (Chrome DevTools MCP, Playwright, Agent Browser), E2E Testing
<input_format_guide>
```json
```jsonc
{
"task_id": "string",
"plan_id": "string",
@@ -54,7 +53,7 @@ Browser Automation (Chrome DevTools MCP, Playwright, Agent Browser), E2E Testing
<output_format_guide>
```json
```jsonc
{
"status": "completed|failed|in_progress|needs_revision",
"task_id": "[task_id]",
@@ -93,7 +92,7 @@ Browser Automation (Chrome DevTools MCP, Playwright, Agent Browser), E2E Testing
- 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.
- Retry: If verification fails, retry up to 3 times. Log each retry: "Retry N/3 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 must be raw JSON 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.