mirror of https://github.com/github/awesome-copilot.git synced 2026-03-20 16:15:12 +00:00

Files

Muhammad Ubaid Raza 720d8b5236 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 14:01:28 +11:00

.gitkeep

Partners (#354 )

2025-10-29 06:07:13 +11:00

README.agents.md

Added one-shot feature planning agent (#1072 )

2026-03-20 10:13:38 +11:00

README.hooks.md

Add tool guardian hook (#1044 )

2026-03-19 16:06:48 +11:00

README.instructions.md

New GitHub Instruction: object orientated programming design patterns as GoF and SOLID (#1012 )

2026-03-16 10:43:53 +11:00

README.plugins.md

gem-team: Add tracing to browser-tester, and improve agent docs and constraints (#1094 )

2026-03-20 14:01:28 +11:00

README.skills.md

feat: add spring-boot-testing skill for Spring Boot 4.0 (#1085 )

2026-03-20 10:24:37 +11:00

README.workflows.md

Merge branch 'staged' into aw/relevance-check

2026-02-27 10:24:59 +11:00

README.workflows.md

⚡ 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