mirror of https://github.com/github/awesome-copilot.git synced 2026-04-11 02:35:55 +00:00

Files

Dan Velton 994e443df1 Add roundup plugin: self-configuring status briefing generator (#1157 )

* Add roundup plugin: self-configuring status briefing generator

Adds a new plugin with two skills:

- roundup-setup: Interactive onboarding that learns the user's communication
  style from examples, discovers available data sources, and builds audience
  profiles. Writes a persistent config to ~/.config/roundup/config.md.

- roundup: Generates draft status briefings on demand by pulling from
  configured sources (GitHub, M365, Slack, Google Workspace, etc.) and
  synthesizing in the user's learned style for any defined audience.

Platform-agnostic by design -- adapts to whatever MCP tools are available
in the user's environment rather than assuming specific integrations.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Address PR review comments

- Fix 'use roundup' help text to clarify multi-audience behavior instead
  of referencing a nonexistent 'default audience'
- Split bundled 'who do you report to + who is on your team' into two
  separate ask_user questions per the one-question-at-a-time rule
- Specify ~/Desktop as explicit save path with fallback prompt when
  directory doesn't exist
- Tables in README verified as correct markdown (single | delimiters)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Improve example-pasting UX in setup flow

- Make 'paste the whole thing right here' explicit so users aren't
  unsure about what/how much to paste
- Confirm receipt more clearly ('grabbed all of that')
- Reframe second example prompt to explain why a second helps
- Cap follow-up asks at two so it doesn't feel nagging
- Note that messy formatting is fine

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Reinforce that more examples = better output

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

2026-03-26 09:55:31 +11:00

.gitkeep

Partners (#354 )

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

README.agents.md

Add TaxCore technical writer agent (#1063 )

2026-03-26 09:54:39 +11:00

README.hooks.md

Add tool guardian hook (#1044 )

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

README.instructions.md

Update to markdown.instructions.md and addition of GFM and generic markdown instructions - Fixes #1108 (#1109 )

2026-03-24 09:31:15 +11:00

README.plugins.md

Add roundup plugin: self-configuring status briefing generator (#1157 )

2026-03-26 09:55:31 +11:00

README.skills.md

Add roundup plugin: self-configuring status briefing generator (#1157 )

2026-03-26 09:55:31 +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