Files
awesome-copilot/docs
Muhammad Ubaid Raza ef40bff1da [gem-team] token, tool call and request optimziations (#1625)
* feat: move to xml top tags for ebtter llm parsing and structure

- Orchestrator is now purely an orchestrator
- Added new calrify  phase for immediate user erequest understanding and task parsing before workflow
- Enforce review/ critic to plan instea dof 3x plan generation retries for better error handling and self-correction
- Add hins to all agents
- Optimize defitons for simplicity/ conciseness while maintaining clarity

* feat(critic): add holistic review and final review enhancements

* chore: bump marketplace version to 1.10.0

- Updated `.github/plugin/marketplace.json` to version 1.10.0.
- Revised `agents/gem-browser-tester.agent.md` to improve the BROWSER TESTER role documentation with a clearer structure, explicit role header, and organized knowledge sources section.

* refactor: streamline verification and self‑critique steps across browser‑tester, code‑simplifier, critic, and debugger agents

* feat(researcher): improve mode selection workflow and research implementation details

- Refine **Clarify** mode description to emphasize minimal research for detecting ambiguities.
- Reorder steps and clarify intent detection (`continue_plan`, `modify_plan`, `new_task`).
- Add explicit sub‑steps for presenting architectural and task‑specific clarifications.
- Update **Research** mode section with clearer initialization workflow.
- Simplify and reformat the confidence calculation comments for readability.
- Minor formatting tweaks and added blank lines for visual separation.

* Update gem-orchestrator.agent.md

* docs(gem-browser-tester): enhance BROWSER TESTER role description and clarify workflow steps- Expanded the BROWSER TESTER role with explicit responsibilities and constraints
- Reformatted the Knowledge Sources list using consistent numbered items for readability- Updated the Workflow section to detail initialization, execution, and teardown steps more clearly- Refined the Output Format and Research Format Guide structures to use proper markdown syntax
- Improved overall formatting and consistency of documentation for better maintainability

* docs: fix typo in delegation description

* feat(metadata): bump marketplace version to 1.15.0 and enrich agent documentation

The marketplace plugin metadata has been updated to reflect the newer
self‑learning multi‑agent orchestration description and the version hasbeen upgraded from 1.13.0 to 1.15.0.

Documentation for the following agents has been expanded with new
sections:

- **gem-browser-tester.agent.md** – added an “Output” section outlining
  strict JSON output rules and a new “I/O Optimization” section covering
  parallel batch operations, read efficiency, and scoping techniques.

- **gem-code-simplifier.agent.md** – similarly added “Output” and
  “I/O Optimization” sections describing concisely formatted JSON,
  parallel I/O, and batch processing best practices.

- **gem-reviewer.agent.md** – updated its output format and added
  detailed guidance on review scope, anti‑patterns, and I/O strategies.

These changes provide clearer usage instructions and performance‑focused
recommendations for the agents while aligning the marketplace metadata
with the updated version.

* feat(plugin): add agents list and README for gem-team plugin

* docs: update readme

* chore: match version with gem-team

* docs: standardize execution order and output format sections in agent documentation

* docs: fix typo in agent documentation files

* refactor: replace "framework" with "harness" in gem‑team marketplace, plugin, and README descriptions
2026-05-06 10:01:10 +10:00
..
2025-10-29 06:07:13 +11:00
2026-03-19 16:06:48 +11:00

Agentic Workflows

Agentic Workflows are AI-powered repository automations that run coding agents in GitHub Actions. Defined in markdown with natural language instructions, they enable event-triggered and scheduled automation with built-in guardrails and security-first design.

How to Contribute

See CONTRIBUTING.md for guidelines on how to contribute new workflows, improve existing ones, and share your use cases.

How to Use Agentic Workflows

What's Included:

  • Each workflow is a single .md file with YAML frontmatter and natural language instructions
  • Workflows are compiled to .lock.yml GitHub Actions files via gh aw compile
  • Workflows follow the GitHub Agentic Workflows specification

To Install:

  • Install the gh aw CLI extension: gh extension install github/gh-aw
  • Copy the workflow .md file to your repository's .github/workflows/ directory
  • Compile with gh aw compile to generate the .lock.yml file
  • Commit both the .md and .lock.yml files

To Activate/Use:

  • Workflows run automatically based on their configured triggers (schedules, events, slash commands)
  • Use gh aw run <workflow> to trigger a manual run
  • Monitor runs with gh aw status and gh aw logs

When to Use:

  • Automate issue triage and labeling
  • Generate daily status reports
  • Maintain documentation automatically
  • Run scheduled code quality checks
  • Respond to slash commands in issues and PRs
  • Orchestrate multi-step repository automation
Name Description Triggers
Daily Issues Report Generates a daily summary of open issues and recent activity as a GitHub issue schedule
OSPO Contributors Report Monthly contributor activity metrics across an organization's repositories. schedule, workflow_dispatch
OSPO Organization Health Report Comprehensive weekly health report for a GitHub organization. Surfaces stale issues/PRs, merge time analysis, contributor leaderboards, and actionable items needing human attention. schedule, workflow_dispatch
OSPO Stale Repository Report Identifies inactive repositories in your organization and generates an archival recommendation report. schedule, workflow_dispatch
OSS Release Compliance Checker Analyzes a target repository against open source release requirements and posts a detailed compliance report as an issue comment. issues, workflow_dispatch
Relevance Check Slash command to evaluate whether an issue or pull request is still relevant to the project slash_command, roles
Relevance Summary Manually triggered workflow that summarizes all open issues and PRs with a /relevance-check response into a single issue workflow_dispatch
Weekly Comment Sync Weekly workflow that finds stale code comments or README snippets, makes text-only synchronization updates, and opens a draft pull request when changes are needed. schedule, workflow_dispatch