You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upgrade gh-aw to v0.87.2 and drop the copilot CLI toolcache workarounds
Both bugs this repo was working around are fixed upstream in v0.87.1, so the
local shims added in #571 are no longer needed.
github/gh-aw#53481 (toolcache ENOENT) - install_copilot_cli.sh now always
materializes ${INSTALL_DIR}/copilot with a wrapper instead of returning early
when GITHUB_PATH is set, and hard-fails if the path is still missing, so the
failure can never again be a silent ENOENT. Verified present in the pinned
action SHA b304200a (gh-aw-actions v0.87.2).
github/gh-aw#52777 (unpinned dispatcher action) - the centralized
slash-command dispatcher now wires a real SHAResolver instead of nil, so
agentic_commands.yml pins the setup action by SHA like every other generated
workflow.
Removed from all three workflows:
- the `pre-agent-steps` wrapper (agent job)
- the `safe-outputs.threat-detection.steps` shim (detection job)
Also in this upgrade:
- v0.87.x enables strict mode by default ("workflows default to strict mode
unless frontmatter sets strict: false"). That surfaced two schema changes,
both applied via `gh aw fix` rather than by hand:
* daily-issue-triage needs an explicit `tools.bash: false` +
`cli-proxy: false`, because upstream agentics sets
`github.min-integrity: none` and strict mode requires shell access to
be intentional. Triage needs no shell, so both are disabled.
* `expires: 60` -> `expires: 60d` (integer to day-string migration).
- The dispatcher skill/agent moved to the v0.87 layout:
.github/agents/agentic-workflows.agent.md is now
.github/agents/agentic-workflows.md, plus a new
.github/skills/agentic-workflows/SKILL.md.
.gitattributes: extend the LF rules from #558 to the generated files they
missed - agentic_commands.yml, agentics-maintenance.yml,
copilot-setup-steps.yml, .github/agents/** and .github/skills/**. Those were
still being checked out as CRLF, which is exactly what makes `gh aw update`
conflict on whole files. Listed individually rather than via *.yml so the
hand-written CI workflows keep the repo default.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: addb9717-56f3-4aa7-a1ed-9d4dd7b43f83
Copy file name to clipboardExpand all lines: .github/agents/agentic-workflows.md
+30-33Lines changed: 30 additions & 33 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,19 +1,27 @@
1
1
---
2
-
description: GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing
2
+
name: Agentic Workflows
3
+
description: GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.
3
4
disable-model-invocation: true
4
5
---
5
6
6
7
# GitHub Agentic Workflows Agent
7
8
8
9
This agent helps you work with **GitHub Agentic Workflows (gh-aw)**, a CLI extension for creating AI-powered workflows in natural language using markdown files.
9
10
11
+
## Repository Instructions Overlay
12
+
13
+
If `.github/aw/instructions.md` exists, load it with:
14
+
@.github/aw/instructions.md
15
+
16
+
Precedence: repository overlay instructions override defaults in this agent when they conflict.
17
+
10
18
## What This Agent Does
11
19
12
20
This is a **dispatcher agent** that routes your request to the appropriate specialized prompt based on your task:
13
21
14
22
-**Creating new workflows**: Routes to `create` prompt
15
23
-**Updating existing workflows**: Routes to `update` prompt
16
-
-**Debugging workflows**: Routes to `debug` prompt
24
+
-**Debugging workflows**: Routes to `debug` prompt
17
25
-**Upgrading workflows**: Routes to `upgrade-agentic-workflows` prompt
18
26
-**Creating report-generating workflows**: Routes to `report` prompt — consult this whenever the workflow posts status updates, audits, analyses, or any structured output as issues, discussions, or comments
19
27
-**Creating shared components**: Routes to `create-shared-agentic-workflow` prompt
@@ -24,9 +32,6 @@ This is a **dispatcher agent** that routes your request to the appropriate speci
24
32
-**Reducing token consumption / cost optimization**: Routes to `token-optimization` guide — consult this whenever the user asks how to reduce token usage, lower costs, speed up workflows, or measure the impact of prompt changes with experiments
25
33
-**Choosing workflow architectures and design patterns**: Routes to `patterns` guide — consult this whenever the user asks for strategy, architecture, operating models, or pattern selection for agentic workflows
26
34
27
-
> [!IMPORTANT]
28
-
> For architecture/pattern-selection requests, load `https://github.com/github/gh-aw/blob/v0.76.1/.github/aw/patterns.md` first.
29
-
30
35
Workflows may optionally include:
31
36
32
37
-**Project tracking / monitoring** (GitHub Projects updates, status reporting)
@@ -37,7 +42,7 @@ Workflows may optionally include:
37
42
- Workflow files: `.github/workflows/*.md` and `.github/workflows/**/*.md`
@@ -56,30 +61,32 @@ When you interact with this agent, it will:
56
61
57
62
## Available Prompts
58
63
64
+
> **Note**: The prompt and reference files listed below are located in the [`github/gh-aw`](https://github.com/github/gh-aw) repository and are **not available locally** in this repository. Load them from their public URLs.
65
+
59
66
### Create New Workflow
60
67
**Load when**: User wants to create a new workflow from scratch, add automation, or design a workflow that doesn't exist yet
@@ -99,7 +106,7 @@ When you interact with this agent, it will:
99
106
### Create a Report-Generating Workflow
100
107
**Load when**: The workflow being created or updated produces reports — recurring status updates, audit summaries, analyses, or any structured output posted as a GitHub issue, discussion, or comment
- "Create a shared component for Notion integration"
@@ -119,7 +126,7 @@ When you interact with this agent, it will:
119
126
### Fix Dependabot PRs
120
127
**Load when**: User needs to close or fix open Dependabot PRs that update dependencies in generated manifest files (`.github/workflows/package.json`, `.github/workflows/requirements.txt`, `.github/workflows/go.mod`)
- "Fix the open Dependabot PRs for npm dependencies"
@@ -129,27 +136,17 @@ When you interact with this agent, it will:
129
136
### Analyze Test Coverage
130
137
**Load when**: The workflow reads, analyzes, or reports test coverage — whether triggered by a PR, a schedule, or a slash command. Always consult this prompt before designing the coverage data strategy.
- "Create a workflow that comments coverage on PRs"
136
143
- "Analyze coverage trends over time"
137
144
- "Add a coverage gate that blocks PRs below a threshold"
138
145
139
-
### Render ASCII Charts in Markdown
140
-
**Load when**: The workflow needs in-markdown charts (sparklines, bars, table+trend views) that must align cleanly and render reliably across GitHub surfaces, including mobile.
- "Show a compact trend chart in an issue comment"
146
-
- "Render a dashboard table with sparkline trends"
147
-
- "Generate aligned ASCII bars for service metrics"
148
-
149
146
### CLI Commands Reference
150
147
**Load when**: The user asks how to run, compile, debug, or manage workflows from the command line; needs the MCP tool equivalent of a `gh aw` command; or is in a restricted environment (e.g., Copilot Cloud) without direct CLI access.
- "How do I trigger workflow X on the main branch?"
@@ -160,7 +157,7 @@ When you interact with this agent, it will:
160
157
### Token Consumption Optimization
161
158
**Load when**: The user asks how to reduce token usage, lower workflow costs, make a workflow faster or cheaper, or measure the impact of prompt or configuration changes.
- "Which pattern should I use for multi-repo rollout?"
@@ -186,7 +183,7 @@ When you interact with this agent, it will:
186
183
When a user interacts with you:
187
184
188
185
1.**Identify the task type** from the user's request
189
-
2.**Load the appropriate prompt** from the GitHub repository URLs listed above
186
+
2.**Load the appropriate prompt** from the URLs listed above
190
187
3.**Follow the loaded prompt's instructions** exactly
191
188
4.**If uncertain**, ask clarifying questions to determine the right prompt
192
189
@@ -225,12 +222,12 @@ gh aw compile --validate
225
222
226
223
## Important Notes
227
224
228
-
- Always reference the instructions file at https://github.com/github/gh-aw/blob/v0.76.1/.github/aw/github-agentic-workflows.md for complete documentation
225
+
- Always reference the instructions file at `https://raw.githubusercontent.com/github/gh-aw/main/.github/aw/github-agentic-workflows.md` for complete documentation
229
226
- Use the MCP tool `agentic-workflows` when running in GitHub Copilot Cloud
230
227
- Workflows must be compiled to `.lock.yml` files before running in GitHub Actions
231
228
-**Bash tools are enabled by default** - Don't restrict bash commands unnecessarily since workflows are sandboxed by the AWF
232
229
- Follow security best practices: minimal permissions, explicit network access, no template injection
233
-
-**Network configuration**: Use ecosystem identifiers (`node`, `python`, `go`, etc.) or explicit FQDNs in `network.allowed`. Bare shorthands like `npm` or `pypi` are **not** valid. See https://github.com/github/gh-aw/blob/v0.76.1/.github/aw/network.md for the full list of valid ecosystem identifiers and domain patterns.
230
+
-**Network configuration**: Use ecosystem identifiers (`node`, `python`, `go`, etc.) or explicit FQDNs in `network.allowed`. Bare shorthands like `npm` or `pypi` are **not** valid. See `https://raw.githubusercontent.com/github/gh-aw/main/.github/aw/network.md` for the full list of valid ecosystem identifiers and domain patterns.
234
231
-**Single-file output**: When creating a workflow, produce exactly **one** workflow `.md` file. Do not create separate documentation files (architecture docs, runbooks, usage guides, etc.). If documentation is needed, add a brief `## Usage` section inside the workflow file itself.
235
232
-**Triggering runs**: Always use `gh aw run <workflow-name>` to trigger a workflow on demand — not `gh workflow run <file>.lock.yml`. `gh aw run` handles workflow resolution by short name, input parsing and validation, and correct run-tracking for agentic workflows. Use `--ref <branch>` to run on a specific branch.
236
-
-**CLI commands reference**: For a complete guide on all `gh aw` commands and their MCP tool equivalents (for restricted environments), see https://github.com/github/gh-aw/blob/v0.76.1/.github/aw/cli-commands.md
233
+
-**CLI commands reference**: For a complete guide on all `gh aw` commands and their MCP tool equivalents (for restricted environments), see `https://raw.githubusercontent.com/github/gh-aw/main/.github/aw/cli-commands.md`
description: Route gh-aw workflow design/create/debug/upgrade requests to the right prompts.
4
+
---
5
+
6
+
# Agentic Workflows Router
7
+
8
+
Use this skill when a user asks to design, create, update, debug, or upgrade GitHub Agentic Workflows in this repository.
9
+
10
+
This skill is a dispatcher: identify the task type, load the matching workflow prompt/skill file, and follow it directly. Keep responses concise and ask a clarifying question if the correct prompt is unclear.
11
+
12
+
Repository overlay (optional):
13
+
- If `.github/aw/instructions.md` exists, load it with `@.github/aw/instructions.md` after loading the matched prompt/skill.
14
+
- Precedence: repository overlay instructions override upstream defaults when they conflict.
15
+
16
+
Read only the files you need:
17
+
Load these files from `github/gh-aw` (they are not available locally).
- Map CLI commands to MCP usage: `.github/aw/cli-commands.md`
103
+
- Choose workflow architecture and patterns: `.github/aw/patterns.md`
104
+
- Optimize token usage and cost: `.github/aw/token-optimization.md`
105
+
- Design long-running multi-agent research workflows: `.github/aw/multi-agent-research.md`
106
+
107
+
When the task involves OTEL, OTLP, traces, observability backends, or telemetry-driven analysis, also read and follow `skills/otel-queries/SKILL.md` after loading the matching workflow prompt or skill.
0 commit comments