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
@@ -54,10 +54,12 @@ When you interact with this agent, it will:
54
54
55
55
## Available Prompts
56
56
57
+
> **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.
58
+
57
59
### Create New Workflow
58
60
**Load when**: User wants to create a new workflow from scratch, add automation, or design a workflow that doesn't exist yet
@@ -97,7 +99,7 @@ When you interact with this agent, it will:
97
99
### Create a Report-Generating Workflow
98
100
**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"
@@ -117,7 +119,7 @@ When you interact with this agent, it will:
117
119
### Fix Dependabot PRs
118
120
**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"
@@ -127,7 +129,7 @@ When you interact with this agent, it will:
127
129
### Analyze Test Coverage
128
130
**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"
@@ -137,7 +139,7 @@ When you interact with this agent, it will:
137
139
### CLI Commands Reference
138
140
**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?"
@@ -148,7 +150,7 @@ When you interact with this agent, it will:
148
150
### Token Consumption Optimization
149
151
**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?"
@@ -174,7 +176,7 @@ When you interact with this agent, it will:
174
176
When a user interacts with you:
175
177
176
178
1.**Identify the task type** from the user's request
177
-
2.**Load the appropriate prompt** from the repository paths listed above
179
+
2.**Load the appropriate prompt** from the URLs listed above
178
180
3.**Follow the loaded prompt's instructions** exactly
179
181
4.**If uncertain**, ask clarifying questions to determine the right prompt
180
182
@@ -213,12 +215,12 @@ gh aw compile --validate
213
215
214
216
## Important Notes
215
217
216
-
- Always reference the instructions file at `.github/aw/github-agentic-workflows.md` for complete documentation
218
+
- Always reference the instructions file at `https://raw.githubusercontent.com/github/gh-aw/main/.github/aw/github-agentic-workflows.md` for complete documentation
217
219
- Use the MCP tool `agentic-workflows` when running in GitHub Copilot Cloud
218
220
- Workflows must be compiled to `.lock.yml` files before running in GitHub Actions
219
221
-**Bash tools are enabled by default** - Don't restrict bash commands unnecessarily since workflows are sandboxed by the AWF
220
222
- Follow security best practices: minimal permissions, explicit network access, no template injection
221
-
-**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 `.github/aw/network.md` for the full list of valid ecosystem identifiers and domain patterns.
223
+
-**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.
222
224
-**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.
223
225
-**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.
224
-
-**CLI commands reference**: For a complete guide on all `gh aw` commands and their MCP tool equivalents (for restricted environments), see `.github/aw/cli-commands.md`
226
+
-**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`
0 commit comments