From 61103a99f3b2d9a0474d955af717619cbaa70163 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sun, 22 Feb 2026 18:34:03 +0000 Subject: [PATCH 1/7] Initial plan From 976d601c3a40325b2fd6a86ebbebde8356a9c59e Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sun, 22 Feb 2026 19:01:20 +0000 Subject: [PATCH 2/7] Refactor safe outputs prompt: extract static intro to file in actions/setup/md/, wrap in XML tags Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- .../agent-performance-analyzer.lock.yml | 38 +--- .../workflows/agent-persona-explorer.lock.yml | 38 +--- .github/workflows/ai-moderator.lock.yml | 38 +--- .github/workflows/archie.lock.yml | 38 +--- .github/workflows/artifacts-summary.lock.yml | 38 +--- .github/workflows/audit-workflows.lock.yml | 38 +--- .github/workflows/auto-triage-issues.lock.yml | 38 +--- .github/workflows/blog-auditor.lock.yml | 38 +--- .github/workflows/bot-detection.lock.yml | 38 +--- .github/workflows/brave.lock.yml | 38 +--- .../breaking-change-checker.lock.yml | 38 +--- .github/workflows/changeset.lock.yml | 38 +--- .github/workflows/ci-coach.lock.yml | 38 +--- .github/workflows/ci-doctor.lock.yml | 38 +--- .../claude-code-user-docs-review.lock.yml | 38 +--- .../cli-consistency-checker.lock.yml | 38 +--- .../workflows/cli-version-checker.lock.yml | 38 +--- .github/workflows/cloclo.lock.yml | 38 +--- .../workflows/code-scanning-fixer.lock.yml | 38 +--- .github/workflows/code-simplifier.lock.yml | 38 +--- .../commit-changes-analyzer.lock.yml | 38 +--- .github/workflows/contribution-check.lock.yml | 38 +--- .../workflows/copilot-agent-analysis.lock.yml | 38 +--- .../copilot-cli-deep-research.lock.yml | 38 +--- .../copilot-pr-merged-report.lock.yml | 38 +--- .../copilot-pr-nlp-analysis.lock.yml | 38 +--- .../copilot-pr-prompt-analysis.lock.yml | 38 +--- .../copilot-session-insights.lock.yml | 38 +--- .github/workflows/craft.lock.yml | 38 +--- .../daily-assign-issue-to-user.lock.yml | 38 +--- .github/workflows/daily-choice-test.lock.yml | 38 +--- .../workflows/daily-cli-performance.lock.yml | 38 +--- .../workflows/daily-cli-tools-tester.lock.yml | 38 +--- .github/workflows/daily-code-metrics.lock.yml | 38 +--- .../workflows/daily-compiler-quality.lock.yml | 38 +--- .../daily-copilot-token-report.lock.yml | 38 +--- .github/workflows/daily-doc-updater.lock.yml | 38 +--- .github/workflows/daily-fact.lock.yml | 38 +--- .github/workflows/daily-file-diet.lock.yml | 38 +--- .../workflows/daily-firewall-report.lock.yml | 38 +--- .../workflows/daily-issues-report.lock.yml | 38 +--- .../daily-malicious-code-scan.lock.yml | 38 +--- .../daily-mcp-concurrency-analysis.lock.yml | 38 +--- .../daily-multi-device-docs-tester.lock.yml | 38 +--- .github/workflows/daily-news.lock.yml | 38 +--- .../daily-observability-report.lock.yml | 38 +--- .../daily-performance-summary.lock.yml | 38 +--- .github/workflows/daily-regulatory.lock.yml | 38 +--- .../daily-rendering-scripts-verifier.lock.yml | 38 +--- .../workflows/daily-repo-chronicle.lock.yml | 38 +--- .../daily-safe-output-optimizer.lock.yml | 38 +--- .../daily-safe-outputs-conformance.lock.yml | 38 +--- .../workflows/daily-secrets-analysis.lock.yml | 38 +--- .../daily-security-red-team.lock.yml | 38 +--- .github/workflows/daily-semgrep-scan.lock.yml | 38 +--- .../daily-syntax-error-quality.lock.yml | 38 +--- .../daily-team-evolution-insights.lock.yml | 38 +--- .github/workflows/daily-team-status.lock.yml | 38 +--- .../daily-testify-uber-super-expert.lock.yml | 38 +--- .../workflows/daily-workflow-updater.lock.yml | 38 +--- .github/workflows/deep-report.lock.yml | 38 +--- .github/workflows/delight.lock.yml | 38 +--- .github/workflows/dependabot-burner.lock.yml | 38 +--- .../workflows/dependabot-go-checker.lock.yml | 38 +--- .github/workflows/dev-hawk.lock.yml | 38 +--- .github/workflows/dev.lock.yml | 38 +--- .../developer-docs-consolidator.lock.yml | 38 +--- .github/workflows/dictation-prompt.lock.yml | 38 +--- .../workflows/discussion-task-miner.lock.yml | 38 +--- .github/workflows/docs-noob-tester.lock.yml | 38 +--- .github/workflows/draft-pr-cleanup.lock.yml | 38 +--- .../duplicate-code-detector.lock.yml | 38 +--- .../example-workflow-analyzer.lock.yml | 38 +--- .github/workflows/firewall-escape.lock.yml | 38 +--- .../workflows/functional-pragmatist.lock.yml | 38 +--- .../github-mcp-structural-analysis.lock.yml | 38 +--- .../github-mcp-tools-report.lock.yml | 38 +--- .../github-remote-mcp-auth-test.lock.yml | 38 +--- .../workflows/glossary-maintainer.lock.yml | 38 +--- .github/workflows/go-fan.lock.yml | 38 +--- .github/workflows/go-logger.lock.yml | 38 +--- .../workflows/go-pattern-detector.lock.yml | 38 +--- .github/workflows/gpclean.lock.yml | 38 +--- .github/workflows/grumpy-reviewer.lock.yml | 38 +--- .github/workflows/hourly-ci-cleaner.lock.yml | 38 +--- .../workflows/instructions-janitor.lock.yml | 38 +--- .github/workflows/issue-arborist.lock.yml | 38 +--- .github/workflows/issue-monster.lock.yml | 38 +--- .github/workflows/issue-triage-agent.lock.yml | 38 +--- .github/workflows/jsweep.lock.yml | 38 +--- .../workflows/layout-spec-maintainer.lock.yml | 38 +--- .github/workflows/lockfile-stats.lock.yml | 38 +--- .github/workflows/mcp-inspector.lock.yml | 38 +--- .github/workflows/mergefest.lock.yml | 38 +--- .../workflows/notion-issue-summary.lock.yml | 38 +--- .github/workflows/org-health-report.lock.yml | 38 +--- .github/workflows/pdf-summary.lock.yml | 38 +--- .github/workflows/plan.lock.yml | 38 +--- .github/workflows/poem-bot.lock.yml | 38 +--- .github/workflows/portfolio-analyst.lock.yml | 38 +--- .../workflows/pr-nitpick-reviewer.lock.yml | 38 +--- .github/workflows/pr-triage-agent.lock.yml | 38 +--- .../prompt-clustering-analysis.lock.yml | 38 +--- .github/workflows/python-data-charts.lock.yml | 38 +--- .github/workflows/q.lock.yml | 38 +--- .github/workflows/refiner.lock.yml | 38 +--- .github/workflows/release.lock.yml | 38 +--- .../workflows/repo-audit-analyzer.lock.yml | 38 +--- .github/workflows/repo-tree-map.lock.yml | 38 +--- .../repository-quality-improver.lock.yml | 38 +--- .github/workflows/research.lock.yml | 38 +--- .github/workflows/safe-output-health.lock.yml | 38 +--- .../schema-consistency-checker.lock.yml | 38 +--- .github/workflows/scout.lock.yml | 38 +--- .../workflows/security-compliance.lock.yml | 38 +--- .github/workflows/security-review.lock.yml | 38 +--- .../semantic-function-refactor.lock.yml | 38 +--- .github/workflows/sergo.lock.yml | 38 +--- .../workflows/slide-deck-maintainer.lock.yml | 38 +--- .github/workflows/smoke-agent.lock.yml | 38 +--- .github/workflows/smoke-claude.lock.yml | 38 +--- .github/workflows/smoke-codex.lock.yml | 38 +--- .github/workflows/smoke-copilot-arm.lock.yml | 38 +--- .github/workflows/smoke-copilot.lock.yml | 38 +--- .github/workflows/smoke-gemini.lock.yml | 38 +--- .github/workflows/smoke-multi-pr.lock.yml | 38 +--- .github/workflows/smoke-project.lock.yml | 38 +--- .github/workflows/smoke-temporary-id.lock.yml | 38 +--- .github/workflows/smoke-test-tools.lock.yml | 38 +--- .../workflows/stale-repo-identifier.lock.yml | 38 +--- .../workflows/static-analysis-report.lock.yml | 38 +--- .../workflows/step-name-alignment.lock.yml | 38 +--- .github/workflows/sub-issue-closer.lock.yml | 38 +--- .github/workflows/super-linter.lock.yml | 38 +--- .../workflows/technical-doc-writer.lock.yml | 38 +--- .github/workflows/terminal-stylist.lock.yml | 38 +--- .../test-create-pr-error-handling.lock.yml | 38 +--- .github/workflows/test-dispatcher.lock.yml | 38 +--- .../test-project-url-default.lock.yml | 38 +--- .github/workflows/tidy.lock.yml | 38 +--- .github/workflows/typist.lock.yml | 38 +--- .../workflows/ubuntu-image-analyzer.lock.yml | 38 +--- .github/workflows/unbloat-docs.lock.yml | 38 +--- .github/workflows/video-analyzer.lock.yml | 38 +--- .../weekly-editors-health-check.lock.yml | 38 +--- .../workflows/weekly-issue-summary.lock.yml | 38 +--- .../weekly-safe-outputs-spec-review.lock.yml | 38 +--- .github/workflows/workflow-generator.lock.yml | 38 +--- .../workflow-health-manager.lock.yml | 38 +--- .../workflows/workflow-normalizer.lock.yml | 38 +--- .../workflow-skill-extractor.lock.yml | 38 +--- actions/setup/md/safe_outputs_prompt.md | 26 +++ pkg/workflow/prompts_test.go | 31 ++- .../safe_outputs_default_create_issue_test.go | 2 +- pkg/workflow/sh.go | 1 + pkg/workflow/unified_prompt_creation_test.go | 14 +- pkg/workflow/unified_prompt_step.go | 183 ++---------------- pkg/workflow/unified_prompt_step_test.go | 3 +- 158 files changed, 522 insertions(+), 5476 deletions(-) create mode 100644 actions/setup/md/safe_outputs_prompt.md diff --git a/.github/workflows/agent-performance-analyzer.lock.yml b/.github/workflows/agent-performance-analyzer.lock.yml index 1cbba0d554..41ee064b4d 100644 --- a/.github/workflows/agent-performance-analyzer.lock.yml +++ b/.github/workflows/agent-performance-analyzer.lock.yml @@ -112,40 +112,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/repo_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Creating an Issue, Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -166,8 +135,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/agent-persona-explorer.lock.yml b/.github/workflows/agent-persona-explorer.lock.yml index 59561ee7b6..b5a4ef27c8 100644 --- a/.github/workflows/agent-persona-explorer.lock.yml +++ b/.github/workflows/agent-persona-explorer.lock.yml @@ -112,40 +112,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -158,8 +127,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/ai-moderator.lock.yml b/.github/workflows/ai-moderator.lock.yml index f95b11e8f9..6632ef0053 100644 --- a/.github/workflows/ai-moderator.lock.yml +++ b/.github/workflows/ai-moderator.lock.yml @@ -149,40 +149,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding Labels to Issues or Pull Requests, Hiding a Comment, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding Labels to Issues or Pull Requests** To add labels to an issue or pull request, use the add_labels tool from safeoutputs. @@ -199,8 +168,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/archie.lock.yml b/.github/workflows/archie.lock.yml index 72cbc8f272..fba99c2741 100644 --- a/.github/workflows/archie.lock.yml +++ b/.github/workflows/archie.lock.yml @@ -142,40 +142,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -188,8 +157,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/artifacts-summary.lock.yml b/.github/workflows/artifacts-summary.lock.yml index e828d915b1..2a8427e30f 100644 --- a/.github/workflows/artifacts-summary.lock.yml +++ b/.github/workflows/artifacts-summary.lock.yml @@ -110,40 +110,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -156,8 +125,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/audit-workflows.lock.yml b/.github/workflows/audit-workflows.lock.yml index de99c2482f..30a8476c4e 100644 --- a/.github/workflows/audit-workflows.lock.yml +++ b/.github/workflows/audit-workflows.lock.yml @@ -113,40 +113,9 @@ jobs: cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" cat "/opt/gh-aw/prompts/repo_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Uploading Assets, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -167,8 +136,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/auto-triage-issues.lock.yml b/.github/workflows/auto-triage-issues.lock.yml index 2217e3f3e4..c6a314dc29 100644 --- a/.github/workflows/auto-triage-issues.lock.yml +++ b/.github/workflows/auto-triage-issues.lock.yml @@ -127,40 +127,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Adding Labels to Issues or Pull Requests, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -177,8 +146,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/blog-auditor.lock.yml b/.github/workflows/blog-auditor.lock.yml index c69e66ebf7..bf8cbcaba5 100644 --- a/.github/workflows/blog-auditor.lock.yml +++ b/.github/workflows/blog-auditor.lock.yml @@ -111,40 +111,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/playwright_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -157,8 +126,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/bot-detection.lock.yml b/.github/workflows/bot-detection.lock.yml index 0adf3901c3..778600aebe 100644 --- a/.github/workflows/bot-detection.lock.yml +++ b/.github/workflows/bot-detection.lock.yml @@ -110,40 +110,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Updating Issues, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -160,8 +129,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/brave.lock.yml b/.github/workflows/brave.lock.yml index 6d8b32edc5..b5489ff990 100644 --- a/.github/workflows/brave.lock.yml +++ b/.github/workflows/brave.lock.yml @@ -132,40 +132,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -178,8 +147,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/breaking-change-checker.lock.yml b/.github/workflows/breaking-change-checker.lock.yml index 2ae11155f3..759510a3f4 100644 --- a/.github/workflows/breaking-change-checker.lock.yml +++ b/.github/workflows/breaking-change-checker.lock.yml @@ -111,40 +111,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -157,8 +126,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/changeset.lock.yml b/.github/workflows/changeset.lock.yml index ac60d52f0d..250120cff0 100644 --- a/.github/workflows/changeset.lock.yml +++ b/.github/workflows/changeset.lock.yml @@ -138,40 +138,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Updating a Pull Request, Pushing Changes to Branch, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Updating a Pull Request** To update a pull request title or body, use the update_pull_request tool from safeoutputs. @@ -191,8 +160,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/ci-coach.lock.yml b/.github/workflows/ci-coach.lock.yml index acc75bdd58..0a38f2b506 100644 --- a/.github/workflows/ci-coach.lock.yml +++ b/.github/workflows/ci-coach.lock.yml @@ -113,40 +113,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Pull Request** To create a pull request: @@ -164,8 +133,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/ci-doctor.lock.yml b/.github/workflows/ci-doctor.lock.yml index ad347362f2..b42d0b63f2 100644 --- a/.github/workflows/ci-doctor.lock.yml +++ b/.github/workflows/ci-doctor.lock.yml @@ -126,40 +126,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Creating an Issue, Updating Issues, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -180,8 +149,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/claude-code-user-docs-review.lock.yml b/.github/workflows/claude-code-user-docs-review.lock.yml index a39ab152a5..747bc5a400 100644 --- a/.github/workflows/claude-code-user-docs-review.lock.yml +++ b/.github/workflows/claude-code-user-docs-review.lock.yml @@ -106,40 +106,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -152,8 +121,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/cli-consistency-checker.lock.yml b/.github/workflows/cli-consistency-checker.lock.yml index 2973ecdab6..f25db4381e 100644 --- a/.github/workflows/cli-consistency-checker.lock.yml +++ b/.github/workflows/cli-consistency-checker.lock.yml @@ -104,40 +104,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -150,8 +119,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/cli-version-checker.lock.yml b/.github/workflows/cli-version-checker.lock.yml index 75be3ea998..c1d6d0179d 100644 --- a/.github/workflows/cli-version-checker.lock.yml +++ b/.github/workflows/cli-version-checker.lock.yml @@ -111,40 +111,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -157,8 +126,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/cloclo.lock.yml b/.github/workflows/cloclo.lock.yml index 1923766583..04485b1b1d 100644 --- a/.github/workflows/cloclo.lock.yml +++ b/.github/workflows/cloclo.lock.yml @@ -173,40 +173,9 @@ jobs: cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/playwright_prompt.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Creating a Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -228,8 +197,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/code-scanning-fixer.lock.yml b/.github/workflows/code-scanning-fixer.lock.yml index f5c5d6dfb5..d6c0dd30e6 100644 --- a/.github/workflows/code-scanning-fixer.lock.yml +++ b/.github/workflows/code-scanning-fixer.lock.yml @@ -107,40 +107,9 @@ jobs: cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" cat "/opt/gh-aw/prompts/repo_memory_prompt_multi.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Pull Request, Adding Labels to Issues or Pull Requests, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Pull Request** To create a pull request: @@ -162,8 +131,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/code-simplifier.lock.yml b/.github/workflows/code-simplifier.lock.yml index 04f752960b..26d5ab411e 100644 --- a/.github/workflows/code-simplifier.lock.yml +++ b/.github/workflows/code-simplifier.lock.yml @@ -112,40 +112,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Pull Request** To create a pull request: @@ -163,8 +132,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/commit-changes-analyzer.lock.yml b/.github/workflows/commit-changes-analyzer.lock.yml index bb3adb103f..6a854e737b 100644 --- a/.github/workflows/commit-changes-analyzer.lock.yml +++ b/.github/workflows/commit-changes-analyzer.lock.yml @@ -112,40 +112,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -158,8 +127,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/contribution-check.lock.yml b/.github/workflows/contribution-check.lock.yml index 2f8a1e94c2..a00f132daa 100644 --- a/.github/workflows/contribution-check.lock.yml +++ b/.github/workflows/contribution-check.lock.yml @@ -108,40 +108,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Creating an Issue, Adding Labels to Issues or Pull Requests, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -162,8 +131,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/copilot-agent-analysis.lock.yml b/.github/workflows/copilot-agent-analysis.lock.yml index 3395849f5b..88b2b7f0dc 100644 --- a/.github/workflows/copilot-agent-analysis.lock.yml +++ b/.github/workflows/copilot-agent-analysis.lock.yml @@ -113,40 +113,9 @@ jobs: cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" cat "/opt/gh-aw/prompts/repo_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -159,8 +128,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/copilot-cli-deep-research.lock.yml b/.github/workflows/copilot-cli-deep-research.lock.yml index 82cd84b59e..be8237de45 100644 --- a/.github/workflows/copilot-cli-deep-research.lock.yml +++ b/.github/workflows/copilot-cli-deep-research.lock.yml @@ -110,40 +110,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/repo_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -156,8 +125,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/copilot-pr-merged-report.lock.yml b/.github/workflows/copilot-pr-merged-report.lock.yml index 5e09fae1ad..396def8cda 100644 --- a/.github/workflows/copilot-pr-merged-report.lock.yml +++ b/.github/workflows/copilot-pr-merged-report.lock.yml @@ -103,40 +103,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -149,8 +118,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + GH_AW_PROMPT_EOF cat << 'GH_AW_PROMPT_EOF' diff --git a/.github/workflows/copilot-pr-nlp-analysis.lock.yml b/.github/workflows/copilot-pr-nlp-analysis.lock.yml index 1a3f9bb232..13750df4ea 100644 --- a/.github/workflows/copilot-pr-nlp-analysis.lock.yml +++ b/.github/workflows/copilot-pr-nlp-analysis.lock.yml @@ -113,40 +113,9 @@ jobs: cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" cat "/opt/gh-aw/prompts/repo_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Uploading Assets, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -167,8 +136,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/copilot-pr-prompt-analysis.lock.yml b/.github/workflows/copilot-pr-prompt-analysis.lock.yml index 6801543023..ce0c317763 100644 --- a/.github/workflows/copilot-pr-prompt-analysis.lock.yml +++ b/.github/workflows/copilot-pr-prompt-analysis.lock.yml @@ -113,40 +113,9 @@ jobs: cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" cat "/opt/gh-aw/prompts/repo_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -159,8 +128,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/copilot-session-insights.lock.yml b/.github/workflows/copilot-session-insights.lock.yml index ba14338f71..0bbb987b0d 100644 --- a/.github/workflows/copilot-session-insights.lock.yml +++ b/.github/workflows/copilot-session-insights.lock.yml @@ -117,40 +117,9 @@ jobs: cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" cat "/opt/gh-aw/prompts/repo_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Uploading Assets, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -171,8 +140,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/craft.lock.yml b/.github/workflows/craft.lock.yml index 0e65af1f7e..c8bc7bdacd 100644 --- a/.github/workflows/craft.lock.yml +++ b/.github/workflows/craft.lock.yml @@ -128,40 +128,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Pushing Changes to Branch, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -181,8 +150,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-assign-issue-to-user.lock.yml b/.github/workflows/daily-assign-issue-to-user.lock.yml index aacdc86993..d526134d18 100644 --- a/.github/workflows/daily-assign-issue-to-user.lock.yml +++ b/.github/workflows/daily-assign-issue-to-user.lock.yml @@ -104,40 +104,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Assigning to a User, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -154,8 +123,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-choice-test.lock.yml b/.github/workflows/daily-choice-test.lock.yml index 43d0f17bef..cdc96a6ccb 100644 --- a/.github/workflows/daily-choice-test.lock.yml +++ b/.github/workflows/daily-choice-test.lock.yml @@ -104,40 +104,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Reporting Missing Tools or Functionality** To report a missing tool or capability, use the missing_tool tool from safeoutputs. @@ -146,8 +115,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-cli-performance.lock.yml b/.github/workflows/daily-cli-performance.lock.yml index 03b126d959..765f38afaf 100644 --- a/.github/workflows/daily-cli-performance.lock.yml +++ b/.github/workflows/daily-cli-performance.lock.yml @@ -112,40 +112,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/repo_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Creating an Issue, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -162,8 +131,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-cli-tools-tester.lock.yml b/.github/workflows/daily-cli-tools-tester.lock.yml index 0c6c325313..7d4ef21bdf 100644 --- a/.github/workflows/daily-cli-tools-tester.lock.yml +++ b/.github/workflows/daily-cli-tools-tester.lock.yml @@ -105,40 +105,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -151,8 +120,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-code-metrics.lock.yml b/.github/workflows/daily-code-metrics.lock.yml index c20f92a8a0..95ec0d8c4b 100644 --- a/.github/workflows/daily-code-metrics.lock.yml +++ b/.github/workflows/daily-code-metrics.lock.yml @@ -113,40 +113,9 @@ jobs: cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" cat "/opt/gh-aw/prompts/repo_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Uploading Assets, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -167,8 +136,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-compiler-quality.lock.yml b/.github/workflows/daily-compiler-quality.lock.yml index c57ccafeb4..0eee2c8dad 100644 --- a/.github/workflows/daily-compiler-quality.lock.yml +++ b/.github/workflows/daily-compiler-quality.lock.yml @@ -110,40 +110,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -156,8 +125,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-copilot-token-report.lock.yml b/.github/workflows/daily-copilot-token-report.lock.yml index 01e6a49e37..d1607a1cb7 100644 --- a/.github/workflows/daily-copilot-token-report.lock.yml +++ b/.github/workflows/daily-copilot-token-report.lock.yml @@ -112,40 +112,9 @@ jobs: cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" cat "/opt/gh-aw/prompts/repo_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Uploading Assets, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -166,8 +135,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-doc-updater.lock.yml b/.github/workflows/daily-doc-updater.lock.yml index 8d1278c8cd..ac04e44725 100644 --- a/.github/workflows/daily-doc-updater.lock.yml +++ b/.github/workflows/daily-doc-updater.lock.yml @@ -106,40 +106,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Pull Request** To create a pull request: @@ -157,8 +126,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-fact.lock.yml b/.github/workflows/daily-fact.lock.yml index f44a2db98e..4783a6991d 100644 --- a/.github/workflows/daily-fact.lock.yml +++ b/.github/workflows/daily-fact.lock.yml @@ -90,40 +90,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -136,8 +105,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-file-diet.lock.yml b/.github/workflows/daily-file-diet.lock.yml index 964ff893f0..7749bab396 100644 --- a/.github/workflows/daily-file-diet.lock.yml +++ b/.github/workflows/daily-file-diet.lock.yml @@ -112,40 +112,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -158,8 +127,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-firewall-report.lock.yml b/.github/workflows/daily-firewall-report.lock.yml index d53f8e5009..ab84300c05 100644 --- a/.github/workflows/daily-firewall-report.lock.yml +++ b/.github/workflows/daily-firewall-report.lock.yml @@ -111,40 +111,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Uploading Assets, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -165,8 +134,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-issues-report.lock.yml b/.github/workflows/daily-issues-report.lock.yml index 6237e4cc73..0e5940ff03 100644 --- a/.github/workflows/daily-issues-report.lock.yml +++ b/.github/workflows/daily-issues-report.lock.yml @@ -116,40 +116,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Closing a Discussion, Uploading Assets, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -174,8 +143,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-malicious-code-scan.lock.yml b/.github/workflows/daily-malicious-code-scan.lock.yml index 8a4d0ae9b4..cc8bab1f54 100644 --- a/.github/workflows/daily-malicious-code-scan.lock.yml +++ b/.github/workflows/daily-malicious-code-scan.lock.yml @@ -109,40 +109,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Code Scanning Alert, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Code Scanning Alert** To create a code scanning alert, use the create_code_scanning_alert tool from safeoutputs. @@ -155,8 +124,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-mcp-concurrency-analysis.lock.yml b/.github/workflows/daily-mcp-concurrency-analysis.lock.yml index cfeabea8a3..4053e049f3 100644 --- a/.github/workflows/daily-mcp-concurrency-analysis.lock.yml +++ b/.github/workflows/daily-mcp-concurrency-analysis.lock.yml @@ -110,40 +110,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Creating an Agent Session, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -160,8 +129,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-multi-device-docs-tester.lock.yml b/.github/workflows/daily-multi-device-docs-tester.lock.yml index 3905b5cae3..e3de8f71ce 100644 --- a/.github/workflows/daily-multi-device-docs-tester.lock.yml +++ b/.github/workflows/daily-multi-device-docs-tester.lock.yml @@ -117,40 +117,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/playwright_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Uploading Assets, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -171,8 +140,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-news.lock.yml b/.github/workflows/daily-news.lock.yml index a1920cca4d..f85bccca69 100644 --- a/.github/workflows/daily-news.lock.yml +++ b/.github/workflows/daily-news.lock.yml @@ -114,40 +114,9 @@ jobs: cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" cat "/opt/gh-aw/prompts/repo_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Uploading Assets, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -168,8 +137,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-observability-report.lock.yml b/.github/workflows/daily-observability-report.lock.yml index ee4654ec8f..d8449417a7 100644 --- a/.github/workflows/daily-observability-report.lock.yml +++ b/.github/workflows/daily-observability-report.lock.yml @@ -111,40 +111,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Closing a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -161,8 +130,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-performance-summary.lock.yml b/.github/workflows/daily-performance-summary.lock.yml index a60e997c93..1907f34087 100644 --- a/.github/workflows/daily-performance-summary.lock.yml +++ b/.github/workflows/daily-performance-summary.lock.yml @@ -112,40 +112,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Closing a Discussion, Uploading Assets, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -170,8 +139,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-regulatory.lock.yml b/.github/workflows/daily-regulatory.lock.yml index e1612462fd..c1ace42c61 100644 --- a/.github/workflows/daily-regulatory.lock.yml +++ b/.github/workflows/daily-regulatory.lock.yml @@ -110,40 +110,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Closing a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -160,8 +129,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-rendering-scripts-verifier.lock.yml b/.github/workflows/daily-rendering-scripts-verifier.lock.yml index 43cfc8640a..02d87ff968 100644 --- a/.github/workflows/daily-rendering-scripts-verifier.lock.yml +++ b/.github/workflows/daily-rendering-scripts-verifier.lock.yml @@ -113,40 +113,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Pull Request** To create a pull request: @@ -164,8 +133,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-repo-chronicle.lock.yml b/.github/workflows/daily-repo-chronicle.lock.yml index f0bb446b3c..1daca32671 100644 --- a/.github/workflows/daily-repo-chronicle.lock.yml +++ b/.github/workflows/daily-repo-chronicle.lock.yml @@ -111,40 +111,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Uploading Assets, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -165,8 +134,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-safe-output-optimizer.lock.yml b/.github/workflows/daily-safe-output-optimizer.lock.yml index cd9adfef46..3d716d9388 100644 --- a/.github/workflows/daily-safe-output-optimizer.lock.yml +++ b/.github/workflows/daily-safe-output-optimizer.lock.yml @@ -114,40 +114,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -160,8 +129,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-safe-outputs-conformance.lock.yml b/.github/workflows/daily-safe-outputs-conformance.lock.yml index 1b1725766d..1495cbffc3 100644 --- a/.github/workflows/daily-safe-outputs-conformance.lock.yml +++ b/.github/workflows/daily-safe-outputs-conformance.lock.yml @@ -109,40 +109,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -155,8 +124,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-secrets-analysis.lock.yml b/.github/workflows/daily-secrets-analysis.lock.yml index dc645baec2..1ebac25f9e 100644 --- a/.github/workflows/daily-secrets-analysis.lock.yml +++ b/.github/workflows/daily-secrets-analysis.lock.yml @@ -109,40 +109,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Closing a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -159,8 +128,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-security-red-team.lock.yml b/.github/workflows/daily-security-red-team.lock.yml index 8bd44358c1..ce16466d7a 100644 --- a/.github/workflows/daily-security-red-team.lock.yml +++ b/.github/workflows/daily-security-red-team.lock.yml @@ -110,40 +110,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -156,8 +125,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-semgrep-scan.lock.yml b/.github/workflows/daily-semgrep-scan.lock.yml index 7138e5fbed..24c26b2793 100644 --- a/.github/workflows/daily-semgrep-scan.lock.yml +++ b/.github/workflows/daily-semgrep-scan.lock.yml @@ -109,40 +109,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Code Scanning Alert, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Code Scanning Alert** To create a code scanning alert, use the create_code_scanning_alert tool from safeoutputs. @@ -155,8 +124,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-syntax-error-quality.lock.yml b/.github/workflows/daily-syntax-error-quality.lock.yml index 1fcdec162f..6828653dbc 100644 --- a/.github/workflows/daily-syntax-error-quality.lock.yml +++ b/.github/workflows/daily-syntax-error-quality.lock.yml @@ -109,40 +109,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -155,8 +124,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-team-evolution-insights.lock.yml b/.github/workflows/daily-team-evolution-insights.lock.yml index ef47f6f5d8..b40d2a7b86 100644 --- a/.github/workflows/daily-team-evolution-insights.lock.yml +++ b/.github/workflows/daily-team-evolution-insights.lock.yml @@ -109,40 +109,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -155,8 +124,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-team-status.lock.yml b/.github/workflows/daily-team-status.lock.yml index c46c463d56..158bd11904 100644 --- a/.github/workflows/daily-team-status.lock.yml +++ b/.github/workflows/daily-team-status.lock.yml @@ -118,40 +118,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -164,8 +133,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-testify-uber-super-expert.lock.yml b/.github/workflows/daily-testify-uber-super-expert.lock.yml index d625206769..e401bd1dda 100644 --- a/.github/workflows/daily-testify-uber-super-expert.lock.yml +++ b/.github/workflows/daily-testify-uber-super-expert.lock.yml @@ -114,40 +114,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/repo_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -160,8 +129,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/daily-workflow-updater.lock.yml b/.github/workflows/daily-workflow-updater.lock.yml index de664d63cf..2bc9e1884a 100644 --- a/.github/workflows/daily-workflow-updater.lock.yml +++ b/.github/workflows/daily-workflow-updater.lock.yml @@ -105,40 +105,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Pull Request** To create a pull request: @@ -156,8 +125,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/deep-report.lock.yml b/.github/workflows/deep-report.lock.yml index 77e8e74673..d70023dd3b 100644 --- a/.github/workflows/deep-report.lock.yml +++ b/.github/workflows/deep-report.lock.yml @@ -112,40 +112,9 @@ jobs: cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" cat "/opt/gh-aw/prompts/repo_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Creating a Discussion, Uploading Assets, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -170,8 +139,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/delight.lock.yml b/.github/workflows/delight.lock.yml index f195cf346c..9d80028bc3 100644 --- a/.github/workflows/delight.lock.yml +++ b/.github/workflows/delight.lock.yml @@ -111,40 +111,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/repo_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -161,8 +130,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/dependabot-burner.lock.yml b/.github/workflows/dependabot-burner.lock.yml index 6832290da4..616470a6ae 100644 --- a/.github/workflows/dependabot-burner.lock.yml +++ b/.github/workflows/dependabot-burner.lock.yml @@ -106,40 +106,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -152,8 +121,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/dependabot-go-checker.lock.yml b/.github/workflows/dependabot-go-checker.lock.yml index 9a89640710..c6002ba2ff 100644 --- a/.github/workflows/dependabot-go-checker.lock.yml +++ b/.github/workflows/dependabot-go-checker.lock.yml @@ -104,40 +104,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Closing an Issue, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -154,8 +123,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/dev-hawk.lock.yml b/.github/workflows/dev-hawk.lock.yml index f7b791d914..18773488ec 100644 --- a/.github/workflows/dev-hawk.lock.yml +++ b/.github/workflows/dev-hawk.lock.yml @@ -121,40 +121,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -167,8 +136,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/dev.lock.yml b/.github/workflows/dev.lock.yml index 2f1919afdd..82cfc68b1b 100644 --- a/.github/workflows/dev.lock.yml +++ b/.github/workflows/dev.lock.yml @@ -104,40 +104,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -150,8 +119,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/developer-docs-consolidator.lock.yml b/.github/workflows/developer-docs-consolidator.lock.yml index e5dd673fec..9fb9a53575 100644 --- a/.github/workflows/developer-docs-consolidator.lock.yml +++ b/.github/workflows/developer-docs-consolidator.lock.yml @@ -110,40 +110,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Creating a Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -165,8 +134,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/dictation-prompt.lock.yml b/.github/workflows/dictation-prompt.lock.yml index 846e28884f..b3944965de 100644 --- a/.github/workflows/dictation-prompt.lock.yml +++ b/.github/workflows/dictation-prompt.lock.yml @@ -108,40 +108,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Pull Request** To create a pull request: @@ -159,8 +128,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/discussion-task-miner.lock.yml b/.github/workflows/discussion-task-miner.lock.yml index f37d2e677c..0f4bc8d304 100644 --- a/.github/workflows/discussion-task-miner.lock.yml +++ b/.github/workflows/discussion-task-miner.lock.yml @@ -111,40 +111,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/repo_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Creating an Issue, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -161,8 +130,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/docs-noob-tester.lock.yml b/.github/workflows/docs-noob-tester.lock.yml index f24005d31a..010b54dca0 100644 --- a/.github/workflows/docs-noob-tester.lock.yml +++ b/.github/workflows/docs-noob-tester.lock.yml @@ -110,40 +110,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/playwright_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Uploading Assets, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -164,8 +133,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/draft-pr-cleanup.lock.yml b/.github/workflows/draft-pr-cleanup.lock.yml index da66739b43..ed119ee0ca 100644 --- a/.github/workflows/draft-pr-cleanup.lock.yml +++ b/.github/workflows/draft-pr-cleanup.lock.yml @@ -105,40 +105,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Closing a Pull Request, Adding Labels to Issues or Pull Requests, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -159,8 +128,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/duplicate-code-detector.lock.yml b/.github/workflows/duplicate-code-detector.lock.yml index 68179ec445..56064f5888 100644 --- a/.github/workflows/duplicate-code-detector.lock.yml +++ b/.github/workflows/duplicate-code-detector.lock.yml @@ -106,40 +106,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -152,8 +121,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/example-workflow-analyzer.lock.yml b/.github/workflows/example-workflow-analyzer.lock.yml index 53e5f42f48..7b4a3e3880 100644 --- a/.github/workflows/example-workflow-analyzer.lock.yml +++ b/.github/workflows/example-workflow-analyzer.lock.yml @@ -109,40 +109,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -155,8 +124,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/firewall-escape.lock.yml b/.github/workflows/firewall-escape.lock.yml index 7b815fe471..aab0606ba2 100644 --- a/.github/workflows/firewall-escape.lock.yml +++ b/.github/workflows/firewall-escape.lock.yml @@ -129,40 +129,9 @@ jobs: cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" cat "/opt/gh-aw/prompts/repo_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -175,8 +144,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/functional-pragmatist.lock.yml b/.github/workflows/functional-pragmatist.lock.yml index ea9682228a..55716ea5fa 100644 --- a/.github/workflows/functional-pragmatist.lock.yml +++ b/.github/workflows/functional-pragmatist.lock.yml @@ -108,40 +108,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Pull Request** To create a pull request: @@ -159,8 +128,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/github-mcp-structural-analysis.lock.yml b/.github/workflows/github-mcp-structural-analysis.lock.yml index 198f909bcf..5639505c09 100644 --- a/.github/workflows/github-mcp-structural-analysis.lock.yml +++ b/.github/workflows/github-mcp-structural-analysis.lock.yml @@ -110,40 +110,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Uploading Assets, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -164,8 +133,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/github-mcp-tools-report.lock.yml b/.github/workflows/github-mcp-tools-report.lock.yml index 816855513a..3293ee8c65 100644 --- a/.github/workflows/github-mcp-tools-report.lock.yml +++ b/.github/workflows/github-mcp-tools-report.lock.yml @@ -110,40 +110,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Creating a Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -165,8 +134,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/github-remote-mcp-auth-test.lock.yml b/.github/workflows/github-remote-mcp-auth-test.lock.yml index 0519e6a9d4..cf11b13642 100644 --- a/.github/workflows/github-remote-mcp-auth-test.lock.yml +++ b/.github/workflows/github-remote-mcp-auth-test.lock.yml @@ -106,40 +106,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -152,8 +121,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/glossary-maintainer.lock.yml b/.github/workflows/glossary-maintainer.lock.yml index 39ead29eb0..1814818199 100644 --- a/.github/workflows/glossary-maintainer.lock.yml +++ b/.github/workflows/glossary-maintainer.lock.yml @@ -110,40 +110,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Pull Request** To create a pull request: @@ -161,8 +130,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/go-fan.lock.yml b/.github/workflows/go-fan.lock.yml index 6367d6ff56..efce769752 100644 --- a/.github/workflows/go-fan.lock.yml +++ b/.github/workflows/go-fan.lock.yml @@ -109,40 +109,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -155,8 +124,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/go-logger.lock.yml b/.github/workflows/go-logger.lock.yml index 5ace94e96a..ce08e4d804 100644 --- a/.github/workflows/go-logger.lock.yml +++ b/.github/workflows/go-logger.lock.yml @@ -110,40 +110,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Pull Request** To create a pull request: @@ -161,8 +130,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/go-pattern-detector.lock.yml b/.github/workflows/go-pattern-detector.lock.yml index d8769ac96d..25e6893ff5 100644 --- a/.github/workflows/go-pattern-detector.lock.yml +++ b/.github/workflows/go-pattern-detector.lock.yml @@ -109,40 +109,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -155,8 +124,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/gpclean.lock.yml b/.github/workflows/gpclean.lock.yml index b9696321c1..1beae9539c 100644 --- a/.github/workflows/gpclean.lock.yml +++ b/.github/workflows/gpclean.lock.yml @@ -106,40 +106,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -152,8 +121,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/grumpy-reviewer.lock.yml b/.github/workflows/grumpy-reviewer.lock.yml index 656c25263c..72095495c8 100644 --- a/.github/workflows/grumpy-reviewer.lock.yml +++ b/.github/workflows/grumpy-reviewer.lock.yml @@ -133,40 +133,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Pull Request Review Comment, Submitting a Pull Request Review, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Pull Request Review Comment** To create a pull request review comment, use the create_pull_request_review_comment tool from safeoutputs. @@ -183,8 +152,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/hourly-ci-cleaner.lock.yml b/.github/workflows/hourly-ci-cleaner.lock.yml index 5c39ab1cd0..5b5e0dc73a 100644 --- a/.github/workflows/hourly-ci-cleaner.lock.yml +++ b/.github/workflows/hourly-ci-cleaner.lock.yml @@ -113,40 +113,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Pull Request** To create a pull request: @@ -164,8 +133,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/instructions-janitor.lock.yml b/.github/workflows/instructions-janitor.lock.yml index 12c71ca365..8a1a188ae8 100644 --- a/.github/workflows/instructions-janitor.lock.yml +++ b/.github/workflows/instructions-janitor.lock.yml @@ -106,40 +106,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Pull Request** To create a pull request: @@ -157,8 +126,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/issue-arborist.lock.yml b/.github/workflows/issue-arborist.lock.yml index dae0d23b02..412de9c6c4 100644 --- a/.github/workflows/issue-arborist.lock.yml +++ b/.github/workflows/issue-arborist.lock.yml @@ -109,40 +109,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Creating a Discussion, Linking a Sub-Issue, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -163,8 +132,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/issue-monster.lock.yml b/.github/workflows/issue-monster.lock.yml index 42fd6174e8..1c43859363 100644 --- a/.github/workflows/issue-monster.lock.yml +++ b/.github/workflows/issue-monster.lock.yml @@ -116,40 +116,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Assigning to an Agent, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -166,8 +135,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/issue-triage-agent.lock.yml b/.github/workflows/issue-triage-agent.lock.yml index e219618902..05802d0943 100644 --- a/.github/workflows/issue-triage-agent.lock.yml +++ b/.github/workflows/issue-triage-agent.lock.yml @@ -99,40 +99,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Adding Labels to Issues or Pull Requests, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -149,8 +118,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/jsweep.lock.yml b/.github/workflows/jsweep.lock.yml index 5bdc33729a..26686566e0 100644 --- a/.github/workflows/jsweep.lock.yml +++ b/.github/workflows/jsweep.lock.yml @@ -106,40 +106,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Pull Request** To create a pull request: @@ -157,8 +126,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/layout-spec-maintainer.lock.yml b/.github/workflows/layout-spec-maintainer.lock.yml index b40a3a42c1..dd37502d26 100644 --- a/.github/workflows/layout-spec-maintainer.lock.yml +++ b/.github/workflows/layout-spec-maintainer.lock.yml @@ -106,40 +106,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Pull Request** To create a pull request: @@ -157,8 +126,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/lockfile-stats.lock.yml b/.github/workflows/lockfile-stats.lock.yml index 3cb118cd47..a3002fbfac 100644 --- a/.github/workflows/lockfile-stats.lock.yml +++ b/.github/workflows/lockfile-stats.lock.yml @@ -110,40 +110,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -156,8 +125,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/mcp-inspector.lock.yml b/.github/workflows/mcp-inspector.lock.yml index ab368b8718..f78af7869d 100644 --- a/.github/workflows/mcp-inspector.lock.yml +++ b/.github/workflows/mcp-inspector.lock.yml @@ -124,40 +124,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -170,8 +139,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/mergefest.lock.yml b/.github/workflows/mergefest.lock.yml index 3b3280e17c..85cb33399d 100644 --- a/.github/workflows/mergefest.lock.yml +++ b/.github/workflows/mergefest.lock.yml @@ -126,40 +126,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Pushing Changes to Branch, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Pushing Changes to a Pull Request Branch** To push changes to the branch of a pull request: @@ -175,8 +144,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/notion-issue-summary.lock.yml b/.github/workflows/notion-issue-summary.lock.yml index 4a5357024a..4bb0139dbe 100644 --- a/.github/workflows/notion-issue-summary.lock.yml +++ b/.github/workflows/notion-issue-summary.lock.yml @@ -112,40 +112,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Reporting Missing Tools or Functionality** To report a missing tool or capability, use the missing_tool tool from safeoutputs. @@ -154,8 +123,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/org-health-report.lock.yml b/.github/workflows/org-health-report.lock.yml index 5f57a5db7e..9937a83731 100644 --- a/.github/workflows/org-health-report.lock.yml +++ b/.github/workflows/org-health-report.lock.yml @@ -112,40 +112,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Uploading Assets, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -166,8 +135,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/pdf-summary.lock.yml b/.github/workflows/pdf-summary.lock.yml index d5d6d9cf99..dd96ba6a71 100644 --- a/.github/workflows/pdf-summary.lock.yml +++ b/.github/workflows/pdf-summary.lock.yml @@ -154,40 +154,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -204,8 +173,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/plan.lock.yml b/.github/workflows/plan.lock.yml index 0bbc0283fe..bdad701318 100644 --- a/.github/workflows/plan.lock.yml +++ b/.github/workflows/plan.lock.yml @@ -132,40 +132,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Closing a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -182,8 +151,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/poem-bot.lock.yml b/.github/workflows/poem-bot.lock.yml index 8af7848704..1a92236139 100644 --- a/.github/workflows/poem-bot.lock.yml +++ b/.github/workflows/poem-bot.lock.yml @@ -144,40 +144,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Creating an Issue, Updating Issues, Creating a Discussion, Creating an Agent Session, Creating a Pull Request, Closing a Pull Request, Creating a Pull Request Review Comment, Adding Labels to Issues or Pull Requests, Pushing Changes to Branch, Uploading Assets, Linking a Sub-Issue, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -246,8 +215,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/portfolio-analyst.lock.yml b/.github/workflows/portfolio-analyst.lock.yml index 23ccd48c84..db44e6af39 100644 --- a/.github/workflows/portfolio-analyst.lock.yml +++ b/.github/workflows/portfolio-analyst.lock.yml @@ -112,40 +112,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Uploading Assets, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -166,8 +135,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/pr-nitpick-reviewer.lock.yml b/.github/workflows/pr-nitpick-reviewer.lock.yml index a1cdc5b64a..71ebf0e4a0 100644 --- a/.github/workflows/pr-nitpick-reviewer.lock.yml +++ b/.github/workflows/pr-nitpick-reviewer.lock.yml @@ -161,40 +161,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Creating a Pull Request Review Comment, Submitting a Pull Request Review, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -215,8 +184,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/pr-triage-agent.lock.yml b/.github/workflows/pr-triage-agent.lock.yml index f23e37a263..04f93664f6 100644 --- a/.github/workflows/pr-triage-agent.lock.yml +++ b/.github/workflows/pr-triage-agent.lock.yml @@ -105,40 +105,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/repo_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Creating an Issue, Adding Labels to Issues or Pull Requests, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -159,8 +128,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/prompt-clustering-analysis.lock.yml b/.github/workflows/prompt-clustering-analysis.lock.yml index 40f7f0963e..f725d8f08d 100644 --- a/.github/workflows/prompt-clustering-analysis.lock.yml +++ b/.github/workflows/prompt-clustering-analysis.lock.yml @@ -115,40 +115,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -161,8 +130,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/python-data-charts.lock.yml b/.github/workflows/python-data-charts.lock.yml index 6c934a54f3..83f3cb564a 100644 --- a/.github/workflows/python-data-charts.lock.yml +++ b/.github/workflows/python-data-charts.lock.yml @@ -109,40 +109,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Uploading Assets, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -163,8 +132,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/q.lock.yml b/.github/workflows/q.lock.yml index 4f5bfa197d..e8f7333de9 100644 --- a/.github/workflows/q.lock.yml +++ b/.github/workflows/q.lock.yml @@ -166,40 +166,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Creating a Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -221,8 +190,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/refiner.lock.yml b/.github/workflows/refiner.lock.yml index 1e5cf3603e..b0a28053fe 100644 --- a/.github/workflows/refiner.lock.yml +++ b/.github/workflows/refiner.lock.yml @@ -130,40 +130,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Creating a Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -185,8 +154,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/release.lock.yml b/.github/workflows/release.lock.yml index b195ae24bb..7259d9fe38 100644 --- a/.github/workflows/release.lock.yml +++ b/.github/workflows/release.lock.yml @@ -116,40 +116,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Updating a Release, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Updating a Release** To update a GitHub release description, use the update_release tool from safeoutputs. @@ -162,8 +131,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/repo-audit-analyzer.lock.yml b/.github/workflows/repo-audit-analyzer.lock.yml index 492a2160cb..ef0c477fd4 100644 --- a/.github/workflows/repo-audit-analyzer.lock.yml +++ b/.github/workflows/repo-audit-analyzer.lock.yml @@ -114,40 +114,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt_multi.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -160,8 +129,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/repo-tree-map.lock.yml b/.github/workflows/repo-tree-map.lock.yml index aaa65eea5f..f487e26e1b 100644 --- a/.github/workflows/repo-tree-map.lock.yml +++ b/.github/workflows/repo-tree-map.lock.yml @@ -109,40 +109,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -155,8 +124,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/repository-quality-improver.lock.yml b/.github/workflows/repository-quality-improver.lock.yml index 459a8a5cb6..a0a3cef9c6 100644 --- a/.github/workflows/repository-quality-improver.lock.yml +++ b/.github/workflows/repository-quality-improver.lock.yml @@ -109,40 +109,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt_multi.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -155,8 +124,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/research.lock.yml b/.github/workflows/research.lock.yml index 5d8326c174..6c11eeb3e4 100644 --- a/.github/workflows/research.lock.yml +++ b/.github/workflows/research.lock.yml @@ -113,40 +113,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -159,8 +128,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/safe-output-health.lock.yml b/.github/workflows/safe-output-health.lock.yml index ad25a4c850..c70dd4762e 100644 --- a/.github/workflows/safe-output-health.lock.yml +++ b/.github/workflows/safe-output-health.lock.yml @@ -111,40 +111,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -157,8 +126,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/schema-consistency-checker.lock.yml b/.github/workflows/schema-consistency-checker.lock.yml index d4e40dbe2f..0f84f38827 100644 --- a/.github/workflows/schema-consistency-checker.lock.yml +++ b/.github/workflows/schema-consistency-checker.lock.yml @@ -110,40 +110,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -156,8 +125,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/scout.lock.yml b/.github/workflows/scout.lock.yml index 7978b79838..51b66376f4 100644 --- a/.github/workflows/scout.lock.yml +++ b/.github/workflows/scout.lock.yml @@ -191,40 +191,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -237,8 +206,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/security-compliance.lock.yml b/.github/workflows/security-compliance.lock.yml index 5a4120fddb..5fe55d55b6 100644 --- a/.github/workflows/security-compliance.lock.yml +++ b/.github/workflows/security-compliance.lock.yml @@ -130,40 +130,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/repo_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -176,8 +145,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/security-review.lock.yml b/.github/workflows/security-review.lock.yml index b72c049cf9..ba07d2c2a4 100644 --- a/.github/workflows/security-review.lock.yml +++ b/.github/workflows/security-review.lock.yml @@ -133,40 +133,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Pull Request Review Comment, Submitting a Pull Request Review, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Pull Request Review Comment** To create a pull request review comment, use the create_pull_request_review_comment tool from safeoutputs. @@ -183,8 +152,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/semantic-function-refactor.lock.yml b/.github/workflows/semantic-function-refactor.lock.yml index 82ac6974b9..bfc8e3e117 100644 --- a/.github/workflows/semantic-function-refactor.lock.yml +++ b/.github/workflows/semantic-function-refactor.lock.yml @@ -109,40 +109,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Closing an Issue, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -159,8 +128,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/sergo.lock.yml b/.github/workflows/sergo.lock.yml index 7c7db5e5c8..87c0398a8b 100644 --- a/.github/workflows/sergo.lock.yml +++ b/.github/workflows/sergo.lock.yml @@ -110,40 +110,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -156,8 +125,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/slide-deck-maintainer.lock.yml b/.github/workflows/slide-deck-maintainer.lock.yml index 37f38755ce..403caf539d 100644 --- a/.github/workflows/slide-deck-maintainer.lock.yml +++ b/.github/workflows/slide-deck-maintainer.lock.yml @@ -116,40 +116,9 @@ jobs: cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/playwright_prompt.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Pull Request** To create a pull request: @@ -167,8 +136,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/smoke-agent.lock.yml b/.github/workflows/smoke-agent.lock.yml index 34e9b6a7d7..39631175e6 100644 --- a/.github/workflows/smoke-agent.lock.yml +++ b/.github/workflows/smoke-agent.lock.yml @@ -138,40 +138,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Assigning to an Agent, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -188,8 +157,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/smoke-claude.lock.yml b/.github/workflows/smoke-claude.lock.yml index 7fa032d796..8e0c0d5d1c 100644 --- a/.github/workflows/smoke-claude.lock.yml +++ b/.github/workflows/smoke-claude.lock.yml @@ -158,40 +158,9 @@ jobs: cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/playwright_prompt.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Creating an Issue, Closing a Pull Request, Updating a Pull Request, Creating a Pull Request Review Comment, Submitting a Pull Request Review, Resolving a Pull Request Review Thread, Adding Labels to Issues or Pull Requests, Adding a Reviewer to a Pull Request, Pushing Changes to Branch, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -243,8 +212,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/smoke-codex.lock.yml b/.github/workflows/smoke-codex.lock.yml index d564eb37c9..58de44dc1b 100644 --- a/.github/workflows/smoke-codex.lock.yml +++ b/.github/workflows/smoke-codex.lock.yml @@ -150,40 +150,9 @@ jobs: cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/playwright_prompt.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Creating an Issue, Adding Labels to Issues or Pull Requests, Removing Labels from Issues or Pull Requests, Unassigning from a User, Hiding a Comment, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -216,8 +185,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/smoke-copilot-arm.lock.yml b/.github/workflows/smoke-copilot-arm.lock.yml index b86005293d..102dceaf64 100644 --- a/.github/workflows/smoke-copilot-arm.lock.yml +++ b/.github/workflows/smoke-copilot-arm.lock.yml @@ -150,40 +150,9 @@ jobs: cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/playwright_prompt.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Creating an Issue, Creating a Discussion, Creating a Pull Request Review Comment, Submitting a Pull Request Review, Adding Labels to Issues or Pull Requests, Removing Labels from Issues or Pull Requests, Dispatching a Workflow, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -224,8 +193,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/smoke-copilot.lock.yml b/.github/workflows/smoke-copilot.lock.yml index 09b53eb049..cdb7ebd5f9 100644 --- a/.github/workflows/smoke-copilot.lock.yml +++ b/.github/workflows/smoke-copilot.lock.yml @@ -152,40 +152,9 @@ jobs: cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/playwright_prompt.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Creating an Issue, Creating a Discussion, Creating a Pull Request Review Comment, Submitting a Pull Request Review, Adding Labels to Issues or Pull Requests, Removing Labels from Issues or Pull Requests, Dispatching a Workflow, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -226,8 +195,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/smoke-gemini.lock.yml b/.github/workflows/smoke-gemini.lock.yml index f7c0b15316..3ae8224e8d 100644 --- a/.github/workflows/smoke-gemini.lock.yml +++ b/.github/workflows/smoke-gemini.lock.yml @@ -149,40 +149,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Creating an Issue, Adding Labels to Issues or Pull Requests, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -203,8 +172,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/smoke-multi-pr.lock.yml b/.github/workflows/smoke-multi-pr.lock.yml index 4263854a27..6f7404b6dd 100644 --- a/.github/workflows/smoke-multi-pr.lock.yml +++ b/.github/workflows/smoke-multi-pr.lock.yml @@ -143,40 +143,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Creating a Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -198,8 +167,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/smoke-project.lock.yml b/.github/workflows/smoke-project.lock.yml index 0dd8451067..fddb57ccce 100644 --- a/.github/workflows/smoke-project.lock.yml +++ b/.github/workflows/smoke-project.lock.yml @@ -141,40 +141,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Creating an Issue, Creating a Pull Request, Adding Labels to Issues or Pull Requests, Removing Labels from Issues or Pull Requests, Updating a Project, Creating a Project Status Update, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -216,8 +185,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/smoke-temporary-id.lock.yml b/.github/workflows/smoke-temporary-id.lock.yml index 373a57ce1b..982af6c6bd 100644 --- a/.github/workflows/smoke-temporary-id.lock.yml +++ b/.github/workflows/smoke-temporary-id.lock.yml @@ -141,40 +141,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Creating an Issue, Linking a Sub-Issue, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -195,8 +164,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/smoke-test-tools.lock.yml b/.github/workflows/smoke-test-tools.lock.yml index c11e412d77..2f8eb2ae8e 100644 --- a/.github/workflows/smoke-test-tools.lock.yml +++ b/.github/workflows/smoke-test-tools.lock.yml @@ -140,40 +140,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -186,8 +155,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/stale-repo-identifier.lock.yml b/.github/workflows/stale-repo-identifier.lock.yml index ec47008f53..4d75b723b3 100644 --- a/.github/workflows/stale-repo-identifier.lock.yml +++ b/.github/workflows/stale-repo-identifier.lock.yml @@ -121,40 +121,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Uploading Assets, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -175,8 +144,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/static-analysis-report.lock.yml b/.github/workflows/static-analysis-report.lock.yml index f439ba818a..1f96579081 100644 --- a/.github/workflows/static-analysis-report.lock.yml +++ b/.github/workflows/static-analysis-report.lock.yml @@ -110,40 +110,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -156,8 +125,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/step-name-alignment.lock.yml b/.github/workflows/step-name-alignment.lock.yml index c489e900e2..a12c26f375 100644 --- a/.github/workflows/step-name-alignment.lock.yml +++ b/.github/workflows/step-name-alignment.lock.yml @@ -106,40 +106,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -152,8 +121,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/sub-issue-closer.lock.yml b/.github/workflows/sub-issue-closer.lock.yml index c04a33c5ce..721b3fccdb 100644 --- a/.github/workflows/sub-issue-closer.lock.yml +++ b/.github/workflows/sub-issue-closer.lock.yml @@ -105,40 +105,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Updating Issues, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -155,8 +124,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/super-linter.lock.yml b/.github/workflows/super-linter.lock.yml index 6017f0ea1e..0f808d63c9 100644 --- a/.github/workflows/super-linter.lock.yml +++ b/.github/workflows/super-linter.lock.yml @@ -110,40 +110,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -156,8 +125,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/technical-doc-writer.lock.yml b/.github/workflows/technical-doc-writer.lock.yml index be3871aa22..b2ba56651f 100644 --- a/.github/workflows/technical-doc-writer.lock.yml +++ b/.github/workflows/technical-doc-writer.lock.yml @@ -114,40 +114,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Creating a Pull Request, Uploading Assets, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -177,8 +146,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/terminal-stylist.lock.yml b/.github/workflows/terminal-stylist.lock.yml index 89c2393a1c..80f3f9cf60 100644 --- a/.github/workflows/terminal-stylist.lock.yml +++ b/.github/workflows/terminal-stylist.lock.yml @@ -105,40 +105,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -151,8 +120,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/test-create-pr-error-handling.lock.yml b/.github/workflows/test-create-pr-error-handling.lock.yml index e325dfb22e..2d74cb7da0 100644 --- a/.github/workflows/test-create-pr-error-handling.lock.yml +++ b/.github/workflows/test-create-pr-error-handling.lock.yml @@ -103,40 +103,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Pull Request** To create a pull request: @@ -154,8 +123,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/test-dispatcher.lock.yml b/.github/workflows/test-dispatcher.lock.yml index f3fd586e02..0b1a9ae816 100644 --- a/.github/workflows/test-dispatcher.lock.yml +++ b/.github/workflows/test-dispatcher.lock.yml @@ -101,40 +101,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Dispatching a Workflow, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Dispatching a Workflow** To dispatch a workflow_dispatch event to another workflow, use the dispatch_workflow tool from safeoutputs. @@ -147,8 +116,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/test-project-url-default.lock.yml b/.github/workflows/test-project-url-default.lock.yml index b36ee30fa9..1c443ea296 100644 --- a/.github/workflows/test-project-url-default.lock.yml +++ b/.github/workflows/test-project-url-default.lock.yml @@ -101,40 +101,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Updating a Project, Creating a Project Status Update, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Updating a Project** To create, add items to, or update a project board, use the update_project tool from safeoutputs. @@ -151,8 +120,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/tidy.lock.yml b/.github/workflows/tidy.lock.yml index 01625a76dd..7508a4417e 100644 --- a/.github/workflows/tidy.lock.yml +++ b/.github/workflows/tidy.lock.yml @@ -139,40 +139,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Pull Request, Pushing Changes to Branch, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Pull Request** To create a pull request: @@ -197,8 +166,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/typist.lock.yml b/.github/workflows/typist.lock.yml index 022437a9da..623ab2d211 100644 --- a/.github/workflows/typist.lock.yml +++ b/.github/workflows/typist.lock.yml @@ -108,40 +108,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -154,8 +123,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/ubuntu-image-analyzer.lock.yml b/.github/workflows/ubuntu-image-analyzer.lock.yml index 04c363ed7a..36365981d3 100644 --- a/.github/workflows/ubuntu-image-analyzer.lock.yml +++ b/.github/workflows/ubuntu-image-analyzer.lock.yml @@ -108,40 +108,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Pull Request** To create a pull request: @@ -159,8 +128,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/unbloat-docs.lock.yml b/.github/workflows/unbloat-docs.lock.yml index e9d1888d04..01c43c630a 100644 --- a/.github/workflows/unbloat-docs.lock.yml +++ b/.github/workflows/unbloat-docs.lock.yml @@ -136,40 +136,9 @@ jobs: cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/playwright_prompt.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Creating a Pull Request, Uploading Assets, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -199,8 +168,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/video-analyzer.lock.yml b/.github/workflows/video-analyzer.lock.yml index f47263596e..8824018128 100644 --- a/.github/workflows/video-analyzer.lock.yml +++ b/.github/workflows/video-analyzer.lock.yml @@ -112,40 +112,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -158,8 +127,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/weekly-editors-health-check.lock.yml b/.github/workflows/weekly-editors-health-check.lock.yml index 048d7bd36f..eac8c68939 100644 --- a/.github/workflows/weekly-editors-health-check.lock.yml +++ b/.github/workflows/weekly-editors-health-check.lock.yml @@ -106,40 +106,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/playwright_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Pull Request, Uploading Assets, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Pull Request** To create a pull request: @@ -165,8 +134,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/weekly-issue-summary.lock.yml b/.github/workflows/weekly-issue-summary.lock.yml index 9fd1b4ea56..194022468b 100644 --- a/.github/workflows/weekly-issue-summary.lock.yml +++ b/.github/workflows/weekly-issue-summary.lock.yml @@ -103,40 +103,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/cache_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Discussion, Uploading Assets, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Discussion** To create a discussion, use the create_discussion tool from safeoutputs. @@ -157,8 +126,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/weekly-safe-outputs-spec-review.lock.yml b/.github/workflows/weekly-safe-outputs-spec-review.lock.yml index ffe2222c07..d28f960226 100644 --- a/.github/workflows/weekly-safe-outputs-spec-review.lock.yml +++ b/.github/workflows/weekly-safe-outputs-spec-review.lock.yml @@ -105,40 +105,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating a Pull Request, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating a Pull Request** To create a pull request: @@ -156,8 +125,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/workflow-generator.lock.yml b/.github/workflows/workflow-generator.lock.yml index fb4d46c7dd..a1c6ec0bde 100644 --- a/.github/workflows/workflow-generator.lock.yml +++ b/.github/workflows/workflow-generator.lock.yml @@ -133,40 +133,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Updating Issues, Assigning to an Agent, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Updating an Issue** To update an issue, use the update_issue tool from safeoutputs. @@ -183,8 +152,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/workflow-health-manager.lock.yml b/.github/workflows/workflow-health-manager.lock.yml index fc75299c73..9557341a75 100644 --- a/.github/workflows/workflow-health-manager.lock.yml +++ b/.github/workflows/workflow-health-manager.lock.yml @@ -112,40 +112,9 @@ jobs: cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" cat "/opt/gh-aw/prompts/repo_memory_prompt.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Adding a Comment to an Issue or Pull Request, Creating an Issue, Updating Issues, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Adding a Comment to an Issue or Pull Request** To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. @@ -166,8 +135,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/workflow-normalizer.lock.yml b/.github/workflows/workflow-normalizer.lock.yml index d0a3691e8b..32783ce4af 100644 --- a/.github/workflows/workflow-normalizer.lock.yml +++ b/.github/workflows/workflow-normalizer.lock.yml @@ -109,40 +109,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -155,8 +124,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/.github/workflows/workflow-skill-extractor.lock.yml b/.github/workflows/workflow-skill-extractor.lock.yml index 87f34cb822..0d5f844120 100644 --- a/.github/workflows/workflow-skill-extractor.lock.yml +++ b/.github/workflows/workflow-skill-extractor.lock.yml @@ -109,40 +109,9 @@ jobs: cat "/opt/gh-aw/prompts/xpia.md" cat "/opt/gh-aw/prompts/temp_folder_prompt.md" cat "/opt/gh-aw/prompts/markdown.md" + cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - - GitHub API Access Instructions - - The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - - To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - - Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - - **IMPORTANT - temporary_id format rules:** - - If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) - - If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i - - Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) - - Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 - - INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) - - VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 - - To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - - Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - - Discover available tools from the safeoutputs MCP server. - - **Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - - **Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. - - --- - - ## Creating an Issue, Creating a Discussion, Reporting Missing Tools or Functionality, Reporting Missing Data - - **IMPORTANT**: To perform the actions listed above, use the **safeoutputs** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository. - + **Creating an Issue** To create an issue, use the create_issue tool from safeoutputs. @@ -159,8 +128,7 @@ jobs: To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. - - + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} diff --git a/actions/setup/md/safe_outputs_prompt.md b/actions/setup/md/safe_outputs_prompt.md new file mode 100644 index 0000000000..a389cd45b9 --- /dev/null +++ b/actions/setup/md/safe_outputs_prompt.md @@ -0,0 +1,26 @@ + +GitHub API Access Instructions + +The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. + + +To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool from the safeoutputs MCP server. Simply writing content will NOT work - the workflow requires actual tool calls. + +Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). + +**IMPORTANT - temporary_id format rules:** +- If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) +- If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i +- Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) +- Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 +- INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) +- VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 +- To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate + +Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. + +**Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. + +**Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. + + diff --git a/pkg/workflow/prompts_test.go b/pkg/workflow/prompts_test.go index 1972c518c0..4d7647096a 100644 --- a/pkg/workflow/prompts_test.go +++ b/pkg/workflow/prompts_test.go @@ -36,16 +36,11 @@ func TestGenerateSafeOutputsPromptStep_IncludesWhenEnabled(t *testing.T) { if !strings.Contains(output, "Create prompt with built-in context") { t.Error("Expected unified prompt step to be generated when safe outputs enabled") } - if !strings.Contains(output, "safe output tool") { - t.Error("Expected prompt to mention safe output tools") + // Static intro is now in safe_outputs_prompt.md (referenced by file, not inline) + if !strings.Contains(output, "safe_outputs_prompt.md") { + t.Error("Expected reference to safe_outputs_prompt.md for static safe outputs intro") } - if !strings.Contains(output, "gh CLI is NOT authenticated") { - t.Error("Expected prompt to warn about gh CLI not being authenticated") - } - if !strings.Contains(output, "safeoutputs MCP server") { - t.Error("Expected prompt to mention safeoutputs MCP server") - } - // Verify per-tool instructions are included for create_issue + // Per-tool instructions are still inline if !strings.Contains(output, "create_issue") { t.Error("Expected prompt to include create_issue tool name") } @@ -68,7 +63,7 @@ func TestGenerateSafeOutputsPromptStep_SkippedWhenDisabled(t *testing.T) { output := yaml.String() // Should still have unified step (for temp folder), but not safe outputs - if strings.Contains(output, "") { + if strings.Contains(output, "safe_outputs_prompt.md") { t.Error("Expected safe outputs section to NOT be in unified prompt when disabled") } } @@ -101,9 +96,14 @@ func TestSafeOutputsPrompt_IncludesPerToolInstructions(t *testing.T) { compiler.generateUnifiedPromptStep(&yaml, data) output := yaml.String() - // Verify safe outputs section exists - if !strings.Contains(output, "") { - t.Fatal("Expected safe outputs section in generated prompt") + // Static intro is now in safe_outputs_prompt.md (file reference, not inline) + if !strings.Contains(output, "safe_outputs_prompt.md") { + t.Fatal("Expected safe_outputs_prompt.md file reference in generated prompt") + } + + // Per-tool instructions are wrapped in + if !strings.Contains(output, "") { + t.Fatal("Expected section in generated prompt") } // Verify per-tool instructions are present for each enabled tool @@ -128,11 +128,6 @@ func TestSafeOutputsPrompt_IncludesPerToolInstructions(t *testing.T) { } }) } - - // Verify the MCP server discovery instruction is also present - if !strings.Contains(output, "Discover available tools from the safeoutputs MCP server") { - t.Error("Expected prompt to instruct agent to query MCP server for tools") - } } // ============================================================================ diff --git a/pkg/workflow/safe_outputs_default_create_issue_test.go b/pkg/workflow/safe_outputs_default_create_issue_test.go index 8464afecac..c77a1b2e6f 100644 --- a/pkg/workflow/safe_outputs_default_create_issue_test.go +++ b/pkg/workflow/safe_outputs_default_create_issue_test.go @@ -297,7 +297,7 @@ func TestAutoInjectedCreateIssuePrompt(t *testing.T) { for _, tt := range tests { t.Run(tt.name, func(t *testing.T) { var b strings.Builder - generateSafeOutputsPromptSection(&b, tt.safeOutputs) + generateSafeOutputsPerToolInstructions(&b, tt.safeOutputs) output := b.String() specificInstruction := "**IMPORTANT**: Report your findings or results by creating a GitHub issue" diff --git a/pkg/workflow/sh.go b/pkg/workflow/sh.go index cc656bbc47..82f22a4058 100644 --- a/pkg/workflow/sh.go +++ b/pkg/workflow/sh.go @@ -22,6 +22,7 @@ const ( cacheMemoryPromptMultiFile = "cache_memory_prompt_multi.md" repoMemoryPromptFile = "repo_memory_prompt.md" repoMemoryPromptMultiFile = "repo_memory_prompt_multi.md" + safeOutputsPromptFile = "safe_outputs_prompt.md" ) // GitHub context prompt is kept embedded because it contains GitHub Actions expressions diff --git a/pkg/workflow/unified_prompt_creation_test.go b/pkg/workflow/unified_prompt_creation_test.go index 5f3369f91a..cfbecc282b 100644 --- a/pkg/workflow/unified_prompt_creation_test.go +++ b/pkg/workflow/unified_prompt_creation_test.go @@ -44,7 +44,7 @@ func TestGenerateUnifiedPromptCreationStep_OrderingBuiltinFirst(t *testing.T) { // Find positions of different prompt sections in the output tempFolderPos := strings.Index(output, "temp_folder_prompt.md") playwrightPos := strings.Index(output, "playwright_prompt.md") - safeOutputsPos := strings.Index(output, "") + safeOutputsPos := strings.Index(output, "safe_outputs_prompt.md") userPromptPos := strings.Index(output, "# User Prompt") // Verify all sections are present @@ -398,7 +398,7 @@ func TestGenerateUnifiedPromptCreationStep_SystemTags(t *testing.T) { // Find positions of built-in content tempFolderPos := strings.Index(output, "temp_folder_prompt.md") playwrightPos := strings.Index(output, "playwright_prompt.md") - safeOutputsPos := strings.Index(output, "") + safeOutputsPos := strings.Index(output, "safe_outputs_prompt.md") // Find position of user content userTaskPos := strings.Index(output, "# User Task") @@ -638,7 +638,7 @@ func TestGenerateUnifiedPromptCreationStep_AllToolsCombined(t *testing.T) { assert.Contains(t, output, "playwright_prompt.md", "Should have playwright") assert.Contains(t, output, "cache_memory_prompt.md", "Should have cache memory template") assert.Contains(t, output, "repo_memory_prompt.md", "Should have repo memory template file") - assert.Contains(t, output, "", "Should have safe outputs") + assert.Contains(t, output, "safe_outputs_prompt.md", "Should have safe outputs file reference") assert.Contains(t, output, "", "Should have GitHub context") assert.Contains(t, output, "pr_context_prompt.md", "Should have PR context") @@ -899,16 +899,16 @@ Manage issues based on comments.` lockStr := string(lockContent) - // Verify safe-outputs section is within system tags + // Verify safe-outputs file reference is within system tags systemOpenPos := strings.Index(lockStr, "") systemClosePos := strings.Index(lockStr, "") - safeOutputsPos := strings.Index(lockStr, "") + safeOutputsPos := strings.Index(lockStr, "safe_outputs_prompt.md") - require.NotEqual(t, -1, safeOutputsPos, "Should have safe-outputs section") + require.NotEqual(t, -1, safeOutputsPos, "Should reference safe_outputs_prompt.md") assert.Less(t, systemOpenPos, safeOutputsPos, "Safe outputs should be after system tag opens") assert.Less(t, safeOutputsPos, systemClosePos, "Safe outputs should be before system tag closes") - // Should mention the specific tools + // Should mention the specific tools (per-tool instructions are still inline) assert.Contains(t, lockStr, "create_issue", "Should reference create_issue tool") assert.Contains(t, lockStr, "update_issue", "Should reference update_issue tool") } diff --git a/pkg/workflow/unified_prompt_step.go b/pkg/workflow/unified_prompt_step.go index a578e9b1ed..d6e08d7095 100644 --- a/pkg/workflow/unified_prompt_step.go +++ b/pkg/workflow/unified_prompt_step.go @@ -286,38 +286,18 @@ func (c *Compiler) collectPromptSections(data *WorkflowData) []PromptSection { // 7. Safe outputs instructions (if enabled) if HasSafeOutputsEnabled(data.SafeOutputs) { unifiedPromptLog.Print("Adding safe outputs section") - var safeOutputsBuilder strings.Builder - safeOutputsBuilder.WriteString(` -GitHub API Access Instructions - -The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - - -To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool. Simply writing content will NOT work - the workflow requires actual tool calls. - -Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - -**IMPORTANT - temporary_id format rules:** -- If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) -- If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i -- Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) -- Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 -- INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) -- VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 -- To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - -Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - -Discover available tools from the safeoutputs MCP server. - -**Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - -**Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. -`) - generateSafeOutputsPromptSection(&safeOutputsBuilder, data.SafeOutputs) - safeOutputsBuilder.WriteString("\n") + // Static intro from file (gh CLI warning, temporary ID rules, noop note) sections = append(sections, PromptSection{ - Content: safeOutputsBuilder.String(), + Content: safeOutputsPromptFile, + IsFile: true, + }) + // Per-tool instructions (dynamic, depends on which tools are enabled) + var perToolBuilder strings.Builder + perToolBuilder.WriteString("\n") + generateSafeOutputsPerToolInstructions(&perToolBuilder, data.SafeOutputs) + perToolBuilder.WriteString("") + sections = append(sections, PromptSection{ + Content: perToolBuilder.String(), IsFile: false, }) } @@ -607,143 +587,18 @@ func (c *Compiler) generateUnifiedPromptCreationStep(yaml *strings.Builder, buil var safeOutputsPromptLog = logger.New("workflow:safe_outputs_prompt") -// generateSafeOutputsPromptSection appends per-tool usage instructions for each -// configured safe-output capability. It is called from collectPromptSections to -// inject detailed guidance inside the XML block. -func generateSafeOutputsPromptSection(b *strings.Builder, safeOutputs *SafeOutputsConfig) { +// generateSafeOutputsPerToolInstructions appends per-tool usage instructions for each +// configured safe-output capability. It is called from collectPromptSections to inject +// tool-specific guidance inside the XML block. +// +// The static intro (gh CLI warning, temporary ID rules, noop note) lives in +// actions/setup/md/safe_outputs_prompt.md and is included separately via a file reference. +func generateSafeOutputsPerToolInstructions(b *strings.Builder, safeOutputs *SafeOutputsConfig) { if safeOutputs == nil { return } - safeOutputsPromptLog.Print("Generating safe outputs prompt section") - - // Build heading that lists every enabled capability - b.WriteString("\n---\n\n## ") - written := false - write := func(label string) { - if written { - b.WriteString(", ") - } - b.WriteString(label) - written = true - } - - if safeOutputs.AddComments != nil { - write("Adding a Comment to an Issue or Pull Request") - } - if safeOutputs.CreateIssues != nil { - write("Creating an Issue") - } - if safeOutputs.CloseIssues != nil { - write("Closing an Issue") - } - if safeOutputs.UpdateIssues != nil { - write("Updating Issues") - } - if safeOutputs.CreateDiscussions != nil { - write("Creating a Discussion") - } - if safeOutputs.UpdateDiscussions != nil { - write("Updating a Discussion") - } - if safeOutputs.CloseDiscussions != nil { - write("Closing a Discussion") - } - if safeOutputs.CreateAgentSessions != nil { - write("Creating an Agent Session") - } - if safeOutputs.CreatePullRequests != nil { - write("Creating a Pull Request") - } - if safeOutputs.ClosePullRequests != nil { - write("Closing a Pull Request") - } - if safeOutputs.UpdatePullRequests != nil { - write("Updating a Pull Request") - } - if safeOutputs.MarkPullRequestAsReadyForReview != nil { - write("Marking a Pull Request as Ready for Review") - } - if safeOutputs.CreatePullRequestReviewComments != nil { - write("Creating a Pull Request Review Comment") - } - if safeOutputs.SubmitPullRequestReview != nil { - write("Submitting a Pull Request Review") - } - if safeOutputs.ReplyToPullRequestReviewComment != nil { - write("Replying to a Pull Request Review Comment") - } - if safeOutputs.ResolvePullRequestReviewThread != nil { - write("Resolving a Pull Request Review Thread") - } - if safeOutputs.AddLabels != nil { - write("Adding Labels to Issues or Pull Requests") - } - if safeOutputs.RemoveLabels != nil { - write("Removing Labels from Issues or Pull Requests") - } - if safeOutputs.AddReviewer != nil { - write("Adding a Reviewer to a Pull Request") - } - if safeOutputs.AssignMilestone != nil { - write("Assigning a Milestone") - } - if safeOutputs.AssignToAgent != nil { - write("Assigning to an Agent") - } - if safeOutputs.AssignToUser != nil { - write("Assigning to a User") - } - if safeOutputs.UnassignFromUser != nil { - write("Unassigning from a User") - } - if safeOutputs.PushToPullRequestBranch != nil { - write("Pushing Changes to Branch") - } - if safeOutputs.CreateCodeScanningAlerts != nil { - write("Creating a Code Scanning Alert") - } - if safeOutputs.AutofixCodeScanningAlert != nil { - write("Autofixing a Code Scanning Alert") - } - if safeOutputs.UploadAssets != nil { - write("Uploading Assets") - } - if safeOutputs.UpdateRelease != nil { - write("Updating a Release") - } - if safeOutputs.UpdateProjects != nil { - write("Updating a Project") - } - if safeOutputs.CreateProjects != nil { - write("Creating a Project") - } - if safeOutputs.CreateProjectStatusUpdates != nil { - write("Creating a Project Status Update") - } - if safeOutputs.LinkSubIssue != nil { - write("Linking a Sub-Issue") - } - if safeOutputs.HideComment != nil { - write("Hiding a Comment") - } - if safeOutputs.DispatchWorkflow != nil { - write("Dispatching a Workflow") - } - if safeOutputs.MissingTool != nil { - write("Reporting Missing Tools or Functionality") - } - if safeOutputs.MissingData != nil { - write("Reporting Missing Data") - } - - if !written { - // No specific capabilities listed – nothing more to add. - return - } - - b.WriteString("\n\n") - fmt.Fprintf(b, "**IMPORTANT**: To perform the actions listed above, use the **%s** tools. Do NOT use `gh`, do NOT call the GitHub API directly. You do not have write access to the GitHub repository.\n\n", constants.SafeOutputsMCPServerID) + safeOutputsPromptLog.Print("Generating safe outputs per-tool instructions") if safeOutputs.AddComments != nil { b.WriteString("**Adding a Comment to an Issue or Pull Request**\n\n") diff --git a/pkg/workflow/unified_prompt_step_test.go b/pkg/workflow/unified_prompt_step_test.go index 24fe02dcf9..1fbe992ef6 100644 --- a/pkg/workflow/unified_prompt_step_test.go +++ b/pkg/workflow/unified_prompt_step_test.go @@ -52,7 +52,8 @@ func TestGenerateUnifiedPromptStep_AllSections(t *testing.T) { assert.Contains(t, output, "playwright_prompt.md", "Should include playwright instructions") assert.Contains(t, output, "cache_memory_prompt.md", "Should include cache memory template file") assert.Contains(t, output, "repo_memory_prompt.md", "Should include repo memory template file") - assert.Contains(t, output, "", "Should include safe outputs instructions") + assert.Contains(t, output, "safe_outputs_prompt.md", "Should include safe outputs file reference") + assert.Contains(t, output, "", "Should include per-tool instructions") assert.Contains(t, output, "", "Should include GitHub context") // Verify cache env vars are NOT in the prompt creation step From 22222e8303a5c022013b7b2da0464c2cd513651a Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sun, 22 Feb 2026 19:21:05 +0000 Subject: [PATCH 3/7] Optimize safe outputs prompt for token usage: compact list format and compressed static intro Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- .../agent-performance-analyzer.lock.yml | 20 +- .../workflows/agent-persona-explorer.lock.yml | 12 +- .github/workflows/ai-moderator.lock.yml | 16 +- .github/workflows/archie.lock.yml | 12 +- .github/workflows/artifacts-summary.lock.yml | 12 +- .github/workflows/audit-workflows.lock.yml | 20 +- .github/workflows/auto-triage-issues.lock.yml | 16 +- .github/workflows/blog-auditor.lock.yml | 12 +- .github/workflows/bot-detection.lock.yml | 16 +- .github/workflows/brave.lock.yml | 12 +- .../breaking-change-checker.lock.yml | 12 +- .github/workflows/changeset.lock.yml | 19 +- .github/workflows/ci-coach.lock.yml | 17 +- .github/workflows/ci-doctor.lock.yml | 20 +- .../claude-code-user-docs-review.lock.yml | 12 +- .../cli-consistency-checker.lock.yml | 12 +- .../workflows/cli-version-checker.lock.yml | 12 +- .github/workflows/cloclo.lock.yml | 21 +- .../workflows/code-scanning-fixer.lock.yml | 21 +- .github/workflows/code-simplifier.lock.yml | 17 +- .../commit-changes-analyzer.lock.yml | 12 +- .github/workflows/contribution-check.lock.yml | 20 +- .../workflows/copilot-agent-analysis.lock.yml | 12 +- .../copilot-cli-deep-research.lock.yml | 12 +- .../copilot-pr-merged-report.lock.yml | 12 +- .../copilot-pr-nlp-analysis.lock.yml | 20 +- .../copilot-pr-prompt-analysis.lock.yml | 12 +- .../copilot-session-insights.lock.yml | 20 +- .github/workflows/craft.lock.yml | 19 +- .../daily-assign-issue-to-user.lock.yml | 16 +- .github/workflows/daily-choice-test.lock.yml | 8 +- .../workflows/daily-cli-performance.lock.yml | 16 +- .../workflows/daily-cli-tools-tester.lock.yml | 12 +- .github/workflows/daily-code-metrics.lock.yml | 20 +- .../workflows/daily-compiler-quality.lock.yml | 12 +- .../daily-copilot-token-report.lock.yml | 20 +- .github/workflows/daily-doc-updater.lock.yml | 17 +- .github/workflows/daily-fact.lock.yml | 12 +- .github/workflows/daily-file-diet.lock.yml | 12 +- .../workflows/daily-firewall-report.lock.yml | 20 +- .../workflows/daily-issues-report.lock.yml | 24 +-- .../daily-malicious-code-scan.lock.yml | 12 +- .../daily-mcp-concurrency-analysis.lock.yml | 16 +- .../daily-multi-device-docs-tester.lock.yml | 20 +- .github/workflows/daily-news.lock.yml | 20 +- .../daily-observability-report.lock.yml | 16 +- .../daily-performance-summary.lock.yml | 24 +-- .github/workflows/daily-regulatory.lock.yml | 16 +- .../daily-rendering-scripts-verifier.lock.yml | 17 +- .../workflows/daily-repo-chronicle.lock.yml | 20 +- .../daily-safe-output-optimizer.lock.yml | 12 +- .../daily-safe-outputs-conformance.lock.yml | 12 +- .../workflows/daily-secrets-analysis.lock.yml | 16 +- .../daily-security-red-team.lock.yml | 12 +- .github/workflows/daily-semgrep-scan.lock.yml | 12 +- .../daily-syntax-error-quality.lock.yml | 12 +- .../daily-team-evolution-insights.lock.yml | 12 +- .github/workflows/daily-team-status.lock.yml | 12 +- .../daily-testify-uber-super-expert.lock.yml | 12 +- .../workflows/daily-workflow-updater.lock.yml | 17 +- .github/workflows/deep-report.lock.yml | 24 +-- .github/workflows/delight.lock.yml | 16 +- .github/workflows/dependabot-burner.lock.yml | 12 +- .../workflows/dependabot-go-checker.lock.yml | 16 +- .github/workflows/dev-hawk.lock.yml | 12 +- .github/workflows/dev.lock.yml | 12 +- .../developer-docs-consolidator.lock.yml | 21 +- .github/workflows/dictation-prompt.lock.yml | 17 +- .../workflows/discussion-task-miner.lock.yml | 16 +- .github/workflows/docs-noob-tester.lock.yml | 20 +- .github/workflows/draft-pr-cleanup.lock.yml | 20 +- .../duplicate-code-detector.lock.yml | 12 +- .../example-workflow-analyzer.lock.yml | 12 +- .github/workflows/firewall-escape.lock.yml | 12 +- .../workflows/functional-pragmatist.lock.yml | 17 +- .../github-mcp-structural-analysis.lock.yml | 20 +- .../github-mcp-tools-report.lock.yml | 21 +- .../github-remote-mcp-auth-test.lock.yml | 12 +- .../workflows/glossary-maintainer.lock.yml | 17 +- .github/workflows/go-fan.lock.yml | 12 +- .github/workflows/go-logger.lock.yml | 17 +- .../workflows/go-pattern-detector.lock.yml | 12 +- .github/workflows/gpclean.lock.yml | 12 +- .github/workflows/grumpy-reviewer.lock.yml | 16 +- .github/workflows/hourly-ci-cleaner.lock.yml | 17 +- .../workflows/instructions-janitor.lock.yml | 17 +- .github/workflows/issue-arborist.lock.yml | 20 +- .github/workflows/issue-monster.lock.yml | 16 +- .github/workflows/issue-triage-agent.lock.yml | 16 +- .github/workflows/jsweep.lock.yml | 17 +- .../workflows/layout-spec-maintainer.lock.yml | 17 +- .github/workflows/lockfile-stats.lock.yml | 12 +- .github/workflows/mcp-inspector.lock.yml | 12 +- .github/workflows/mergefest.lock.yml | 15 +- .../workflows/notion-issue-summary.lock.yml | 8 +- .github/workflows/org-health-report.lock.yml | 20 +- .github/workflows/pdf-summary.lock.yml | 16 +- .github/workflows/plan.lock.yml | 16 +- .github/workflows/poem-bot.lock.yml | 68 +------ .github/workflows/portfolio-analyst.lock.yml | 20 +- .../workflows/pr-nitpick-reviewer.lock.yml | 20 +- .github/workflows/pr-triage-agent.lock.yml | 20 +- .../prompt-clustering-analysis.lock.yml | 12 +- .github/workflows/python-data-charts.lock.yml | 20 +- .github/workflows/q.lock.yml | 21 +- .github/workflows/refiner.lock.yml | 21 +- .github/workflows/release.lock.yml | 12 +- .../workflows/repo-audit-analyzer.lock.yml | 12 +- .github/workflows/repo-tree-map.lock.yml | 12 +- .../repository-quality-improver.lock.yml | 12 +- .github/workflows/research.lock.yml | 12 +- .github/workflows/safe-output-health.lock.yml | 12 +- .../schema-consistency-checker.lock.yml | 12 +- .github/workflows/scout.lock.yml | 12 +- .../workflows/security-compliance.lock.yml | 12 +- .github/workflows/security-review.lock.yml | 16 +- .../semantic-function-refactor.lock.yml | 16 +- .github/workflows/sergo.lock.yml | 12 +- .../workflows/slide-deck-maintainer.lock.yml | 17 +- .github/workflows/smoke-agent.lock.yml | 16 +- .github/workflows/smoke-claude.lock.yml | 51 +---- .github/workflows/smoke-codex.lock.yml | 32 +-- .github/workflows/smoke-copilot-arm.lock.yml | 40 +--- .github/workflows/smoke-copilot.lock.yml | 40 +--- .github/workflows/smoke-gemini.lock.yml | 20 +- .github/workflows/smoke-multi-pr.lock.yml | 21 +- .github/workflows/smoke-project.lock.yml | 41 +--- .github/workflows/smoke-temporary-id.lock.yml | 20 +- .github/workflows/smoke-test-tools.lock.yml | 12 +- .../workflows/stale-repo-identifier.lock.yml | 20 +- .../workflows/static-analysis-report.lock.yml | 12 +- .../workflows/step-name-alignment.lock.yml | 12 +- .github/workflows/sub-issue-closer.lock.yml | 16 +- .github/workflows/super-linter.lock.yml | 12 +- .../workflows/technical-doc-writer.lock.yml | 29 +-- .github/workflows/terminal-stylist.lock.yml | 12 +- .../test-create-pr-error-handling.lock.yml | 17 +- .github/workflows/test-dispatcher.lock.yml | 12 +- .../test-project-url-default.lock.yml | 16 +- .github/workflows/tidy.lock.yml | 24 +-- .github/workflows/typist.lock.yml | 12 +- .../workflows/ubuntu-image-analyzer.lock.yml | 17 +- .github/workflows/unbloat-docs.lock.yml | 29 +-- .github/workflows/video-analyzer.lock.yml | 12 +- .../weekly-editors-health-check.lock.yml | 25 +-- .../workflows/weekly-issue-summary.lock.yml | 20 +- .../weekly-safe-outputs-spec-review.lock.yml | 17 +- .github/workflows/workflow-generator.lock.yml | 16 +- .../workflow-health-manager.lock.yml | 20 +- .../workflows/workflow-normalizer.lock.yml | 12 +- .../workflow-skill-extractor.lock.yml | 16 +- actions/setup/md/safe_outputs_prompt.md | 24 +-- pkg/workflow/prompts_test.go | 27 +-- pkg/workflow/unified_prompt_step.go | 184 ++++++------------ 154 files changed, 279 insertions(+), 2524 deletions(-) diff --git a/.github/workflows/agent-performance-analyzer.lock.yml b/.github/workflows/agent-performance-analyzer.lock.yml index 41ee064b4d..a7b59f77b2 100644 --- a/.github/workflows/agent-performance-analyzer.lock.yml +++ b/.github/workflows/agent-performance-analyzer.lock.yml @@ -115,25 +115,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** - - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: add_comment, create_issue, create_discussion, missing_tool, missing_data diff --git a/.github/workflows/agent-persona-explorer.lock.yml b/.github/workflows/agent-persona-explorer.lock.yml index b5a4ef27c8..bfbc22216c 100644 --- a/.github/workflows/agent-persona-explorer.lock.yml +++ b/.github/workflows/agent-persona-explorer.lock.yml @@ -115,17 +115,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, missing_tool, missing_data diff --git a/.github/workflows/ai-moderator.lock.yml b/.github/workflows/ai-moderator.lock.yml index 6632ef0053..25602c353c 100644 --- a/.github/workflows/ai-moderator.lock.yml +++ b/.github/workflows/ai-moderator.lock.yml @@ -152,21 +152,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding Labels to Issues or Pull Requests** - - To add labels to an issue or pull request, use the add_labels tool from safeoutputs. - - **Hiding a Comment** - - To hide a comment, use the hide_comment tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: add_labels, hide_comment, missing_tool, missing_data diff --git a/.github/workflows/archie.lock.yml b/.github/workflows/archie.lock.yml index fba99c2741..7030015d55 100644 --- a/.github/workflows/archie.lock.yml +++ b/.github/workflows/archie.lock.yml @@ -145,17 +145,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** - - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: add_comment, missing_tool, missing_data diff --git a/.github/workflows/artifacts-summary.lock.yml b/.github/workflows/artifacts-summary.lock.yml index 2a8427e30f..37534ddda3 100644 --- a/.github/workflows/artifacts-summary.lock.yml +++ b/.github/workflows/artifacts-summary.lock.yml @@ -113,17 +113,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, missing_tool, missing_data diff --git a/.github/workflows/audit-workflows.lock.yml b/.github/workflows/audit-workflows.lock.yml index 30a8476c4e..fb437ca3f1 100644 --- a/.github/workflows/audit-workflows.lock.yml +++ b/.github/workflows/audit-workflows.lock.yml @@ -116,25 +116,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** + Tools: create_discussion, upload_asset, missing_tool, missing_data - To create a discussion, use the create_discussion tool from safeoutputs. - - **Uploading Assets** - - To upload files as URL-addressable assets: - 1. Use the upload_asset tool from safeoutputs. - 2. Provide the path to the file you want to upload. - 3. The tool will copy the file to a staging area and return a GitHub raw content URL. - 4. Assets are uploaded to an orphaned git branch after workflow completion. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). diff --git a/.github/workflows/auto-triage-issues.lock.yml b/.github/workflows/auto-triage-issues.lock.yml index c6a314dc29..d4c9bd875a 100644 --- a/.github/workflows/auto-triage-issues.lock.yml +++ b/.github/workflows/auto-triage-issues.lock.yml @@ -130,21 +130,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Adding Labels to Issues or Pull Requests** - - To add labels to an issue or pull request, use the add_labels tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, add_labels, missing_tool, missing_data diff --git a/.github/workflows/blog-auditor.lock.yml b/.github/workflows/blog-auditor.lock.yml index bf8cbcaba5..cad7f9a037 100644 --- a/.github/workflows/blog-auditor.lock.yml +++ b/.github/workflows/blog-auditor.lock.yml @@ -114,17 +114,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, missing_tool, missing_data diff --git a/.github/workflows/bot-detection.lock.yml b/.github/workflows/bot-detection.lock.yml index 778600aebe..a9f04d7cb2 100644 --- a/.github/workflows/bot-detection.lock.yml +++ b/.github/workflows/bot-detection.lock.yml @@ -113,21 +113,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Updating an Issue** - - To update an issue, use the update_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, update_issue, missing_tool, missing_data diff --git a/.github/workflows/brave.lock.yml b/.github/workflows/brave.lock.yml index b5489ff990..bb81591cbe 100644 --- a/.github/workflows/brave.lock.yml +++ b/.github/workflows/brave.lock.yml @@ -135,17 +135,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** - - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: add_comment, missing_tool, missing_data diff --git a/.github/workflows/breaking-change-checker.lock.yml b/.github/workflows/breaking-change-checker.lock.yml index 759510a3f4..f61c6bd77c 100644 --- a/.github/workflows/breaking-change-checker.lock.yml +++ b/.github/workflows/breaking-change-checker.lock.yml @@ -114,17 +114,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, missing_tool, missing_data diff --git a/.github/workflows/changeset.lock.yml b/.github/workflows/changeset.lock.yml index 250120cff0..57dac40f58 100644 --- a/.github/workflows/changeset.lock.yml +++ b/.github/workflows/changeset.lock.yml @@ -141,24 +141,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Updating a Pull Request** + Tools: update_pull_request, push_to_pull_request_branch, missing_tool, missing_data - To update a pull request title or body, use the update_pull_request tool from safeoutputs. - - **Pushing Changes to a Pull Request Branch** - - To push changes to the branch of a pull request: - 1. Make any file changes directly in the working directory. - 2. Add and commit your changes to the local copy of the pull request branch. Be careful to add exactly the files you intend, and verify you haven't deleted or changed any files you didn't intend to. - 3. Push the branch to the repo by using the push_to_pull_request_branch tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + push_to_pull_request_branch: commit changes locally (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/ci-coach.lock.yml b/.github/workflows/ci-coach.lock.yml index 0a38f2b506..3f2a79e6eb 100644 --- a/.github/workflows/ci-coach.lock.yml +++ b/.github/workflows/ci-coach.lock.yml @@ -116,22 +116,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Pull Request** + Tools: create_pull_request, missing_tool, missing_data - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/ci-doctor.lock.yml b/.github/workflows/ci-doctor.lock.yml index b42d0b63f2..0d0ce319d9 100644 --- a/.github/workflows/ci-doctor.lock.yml +++ b/.github/workflows/ci-doctor.lock.yml @@ -129,25 +129,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** - - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Updating an Issue** - - To update an issue, use the update_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: add_comment, create_issue, update_issue, missing_tool, missing_data diff --git a/.github/workflows/claude-code-user-docs-review.lock.yml b/.github/workflows/claude-code-user-docs-review.lock.yml index 747bc5a400..d5f7ae56c5 100644 --- a/.github/workflows/claude-code-user-docs-review.lock.yml +++ b/.github/workflows/claude-code-user-docs-review.lock.yml @@ -109,17 +109,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, missing_tool, missing_data diff --git a/.github/workflows/cli-consistency-checker.lock.yml b/.github/workflows/cli-consistency-checker.lock.yml index f25db4381e..91b626ccda 100644 --- a/.github/workflows/cli-consistency-checker.lock.yml +++ b/.github/workflows/cli-consistency-checker.lock.yml @@ -107,17 +107,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, missing_tool, missing_data diff --git a/.github/workflows/cli-version-checker.lock.yml b/.github/workflows/cli-version-checker.lock.yml index c1d6d0179d..336cbbb7a1 100644 --- a/.github/workflows/cli-version-checker.lock.yml +++ b/.github/workflows/cli-version-checker.lock.yml @@ -114,17 +114,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, missing_tool, missing_data diff --git a/.github/workflows/cloclo.lock.yml b/.github/workflows/cloclo.lock.yml index 04485b1b1d..893f2ec560 100644 --- a/.github/workflows/cloclo.lock.yml +++ b/.github/workflows/cloclo.lock.yml @@ -176,26 +176,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** + Tools: add_comment, create_pull_request, missing_tool, missing_data - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/code-scanning-fixer.lock.yml b/.github/workflows/code-scanning-fixer.lock.yml index d6c0dd30e6..99482bf0bf 100644 --- a/.github/workflows/code-scanning-fixer.lock.yml +++ b/.github/workflows/code-scanning-fixer.lock.yml @@ -110,26 +110,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Pull Request** + Tools: create_pull_request, add_labels, missing_tool, missing_data - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Adding Labels to Issues or Pull Requests** - - To add labels to an issue or pull request, use the add_labels tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/code-simplifier.lock.yml b/.github/workflows/code-simplifier.lock.yml index 26d5ab411e..1faf3fce00 100644 --- a/.github/workflows/code-simplifier.lock.yml +++ b/.github/workflows/code-simplifier.lock.yml @@ -115,22 +115,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Pull Request** + Tools: create_pull_request, missing_tool, missing_data - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/commit-changes-analyzer.lock.yml b/.github/workflows/commit-changes-analyzer.lock.yml index 6a854e737b..4a52a0634a 100644 --- a/.github/workflows/commit-changes-analyzer.lock.yml +++ b/.github/workflows/commit-changes-analyzer.lock.yml @@ -115,17 +115,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, missing_tool, missing_data diff --git a/.github/workflows/contribution-check.lock.yml b/.github/workflows/contribution-check.lock.yml index a00f132daa..cc5ccbf9bf 100644 --- a/.github/workflows/contribution-check.lock.yml +++ b/.github/workflows/contribution-check.lock.yml @@ -111,25 +111,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** - - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Adding Labels to Issues or Pull Requests** - - To add labels to an issue or pull request, use the add_labels tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: add_comment, create_issue, add_labels, missing_tool, missing_data diff --git a/.github/workflows/copilot-agent-analysis.lock.yml b/.github/workflows/copilot-agent-analysis.lock.yml index 88b2b7f0dc..095a76d587 100644 --- a/.github/workflows/copilot-agent-analysis.lock.yml +++ b/.github/workflows/copilot-agent-analysis.lock.yml @@ -116,17 +116,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, missing_tool, missing_data diff --git a/.github/workflows/copilot-cli-deep-research.lock.yml b/.github/workflows/copilot-cli-deep-research.lock.yml index be8237de45..68210f3632 100644 --- a/.github/workflows/copilot-cli-deep-research.lock.yml +++ b/.github/workflows/copilot-cli-deep-research.lock.yml @@ -113,17 +113,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, missing_tool, missing_data diff --git a/.github/workflows/copilot-pr-merged-report.lock.yml b/.github/workflows/copilot-pr-merged-report.lock.yml index 396def8cda..e42ecca79b 100644 --- a/.github/workflows/copilot-pr-merged-report.lock.yml +++ b/.github/workflows/copilot-pr-merged-report.lock.yml @@ -106,17 +106,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, missing_tool, missing_data GH_AW_PROMPT_EOF diff --git a/.github/workflows/copilot-pr-nlp-analysis.lock.yml b/.github/workflows/copilot-pr-nlp-analysis.lock.yml index 13750df4ea..7069bfb624 100644 --- a/.github/workflows/copilot-pr-nlp-analysis.lock.yml +++ b/.github/workflows/copilot-pr-nlp-analysis.lock.yml @@ -116,25 +116,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** + Tools: create_discussion, upload_asset, missing_tool, missing_data - To create a discussion, use the create_discussion tool from safeoutputs. - - **Uploading Assets** - - To upload files as URL-addressable assets: - 1. Use the upload_asset tool from safeoutputs. - 2. Provide the path to the file you want to upload. - 3. The tool will copy the file to a staging area and return a GitHub raw content URL. - 4. Assets are uploaded to an orphaned git branch after workflow completion. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). diff --git a/.github/workflows/copilot-pr-prompt-analysis.lock.yml b/.github/workflows/copilot-pr-prompt-analysis.lock.yml index ce0c317763..799893225c 100644 --- a/.github/workflows/copilot-pr-prompt-analysis.lock.yml +++ b/.github/workflows/copilot-pr-prompt-analysis.lock.yml @@ -116,17 +116,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, missing_tool, missing_data diff --git a/.github/workflows/copilot-session-insights.lock.yml b/.github/workflows/copilot-session-insights.lock.yml index 0bbb987b0d..ff79d62845 100644 --- a/.github/workflows/copilot-session-insights.lock.yml +++ b/.github/workflows/copilot-session-insights.lock.yml @@ -120,25 +120,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** + Tools: create_discussion, upload_asset, missing_tool, missing_data - To create a discussion, use the create_discussion tool from safeoutputs. - - **Uploading Assets** - - To upload files as URL-addressable assets: - 1. Use the upload_asset tool from safeoutputs. - 2. Provide the path to the file you want to upload. - 3. The tool will copy the file to a staging area and return a GitHub raw content URL. - 4. Assets are uploaded to an orphaned git branch after workflow completion. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). diff --git a/.github/workflows/craft.lock.yml b/.github/workflows/craft.lock.yml index c8bc7bdacd..a3ec6691c5 100644 --- a/.github/workflows/craft.lock.yml +++ b/.github/workflows/craft.lock.yml @@ -131,24 +131,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** + Tools: add_comment, push_to_pull_request_branch, missing_tool, missing_data - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Pushing Changes to a Pull Request Branch** - - To push changes to the branch of a pull request: - 1. Make any file changes directly in the working directory. - 2. Add and commit your changes to the local copy of the pull request branch. Be careful to add exactly the files you intend, and verify you haven't deleted or changed any files you didn't intend to. - 3. Push the branch to the repo by using the push_to_pull_request_branch tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + push_to_pull_request_branch: commit changes locally (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/daily-assign-issue-to-user.lock.yml b/.github/workflows/daily-assign-issue-to-user.lock.yml index d526134d18..2ac36786d1 100644 --- a/.github/workflows/daily-assign-issue-to-user.lock.yml +++ b/.github/workflows/daily-assign-issue-to-user.lock.yml @@ -107,21 +107,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** - - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Assigning to a User** - - To assign an issue or pull request to a user, use the assign_to_user tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: add_comment, assign_to_user, missing_tool, missing_data diff --git a/.github/workflows/daily-choice-test.lock.yml b/.github/workflows/daily-choice-test.lock.yml index cdc96a6ccb..591e1fbd2a 100644 --- a/.github/workflows/daily-choice-test.lock.yml +++ b/.github/workflows/daily-choice-test.lock.yml @@ -107,13 +107,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: missing_tool, missing_data diff --git a/.github/workflows/daily-cli-performance.lock.yml b/.github/workflows/daily-cli-performance.lock.yml index 765f38afaf..1246102449 100644 --- a/.github/workflows/daily-cli-performance.lock.yml +++ b/.github/workflows/daily-cli-performance.lock.yml @@ -115,21 +115,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** - - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: add_comment, create_issue, missing_tool, missing_data diff --git a/.github/workflows/daily-cli-tools-tester.lock.yml b/.github/workflows/daily-cli-tools-tester.lock.yml index 7d4ef21bdf..7bfb45e62e 100644 --- a/.github/workflows/daily-cli-tools-tester.lock.yml +++ b/.github/workflows/daily-cli-tools-tester.lock.yml @@ -108,17 +108,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, missing_tool, missing_data diff --git a/.github/workflows/daily-code-metrics.lock.yml b/.github/workflows/daily-code-metrics.lock.yml index 95ec0d8c4b..a3570bd182 100644 --- a/.github/workflows/daily-code-metrics.lock.yml +++ b/.github/workflows/daily-code-metrics.lock.yml @@ -116,25 +116,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** + Tools: create_discussion, upload_asset, missing_tool, missing_data - To create a discussion, use the create_discussion tool from safeoutputs. - - **Uploading Assets** - - To upload files as URL-addressable assets: - 1. Use the upload_asset tool from safeoutputs. - 2. Provide the path to the file you want to upload. - 3. The tool will copy the file to a staging area and return a GitHub raw content URL. - 4. Assets are uploaded to an orphaned git branch after workflow completion. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). diff --git a/.github/workflows/daily-compiler-quality.lock.yml b/.github/workflows/daily-compiler-quality.lock.yml index 0eee2c8dad..4f2a240b9d 100644 --- a/.github/workflows/daily-compiler-quality.lock.yml +++ b/.github/workflows/daily-compiler-quality.lock.yml @@ -113,17 +113,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, missing_tool, missing_data diff --git a/.github/workflows/daily-copilot-token-report.lock.yml b/.github/workflows/daily-copilot-token-report.lock.yml index d1607a1cb7..f8dc10ae23 100644 --- a/.github/workflows/daily-copilot-token-report.lock.yml +++ b/.github/workflows/daily-copilot-token-report.lock.yml @@ -115,25 +115,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** + Tools: create_discussion, upload_asset, missing_tool, missing_data - To create a discussion, use the create_discussion tool from safeoutputs. - - **Uploading Assets** - - To upload files as URL-addressable assets: - 1. Use the upload_asset tool from safeoutputs. - 2. Provide the path to the file you want to upload. - 3. The tool will copy the file to a staging area and return a GitHub raw content URL. - 4. Assets are uploaded to an orphaned git branch after workflow completion. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). diff --git a/.github/workflows/daily-doc-updater.lock.yml b/.github/workflows/daily-doc-updater.lock.yml index ac04e44725..0458434861 100644 --- a/.github/workflows/daily-doc-updater.lock.yml +++ b/.github/workflows/daily-doc-updater.lock.yml @@ -109,22 +109,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Pull Request** + Tools: create_pull_request, missing_tool, missing_data - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/daily-fact.lock.yml b/.github/workflows/daily-fact.lock.yml index 4783a6991d..4ff55eb9bf 100644 --- a/.github/workflows/daily-fact.lock.yml +++ b/.github/workflows/daily-fact.lock.yml @@ -93,17 +93,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** - - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: add_comment, missing_tool, missing_data diff --git a/.github/workflows/daily-file-diet.lock.yml b/.github/workflows/daily-file-diet.lock.yml index 7749bab396..9c6ca9cbb8 100644 --- a/.github/workflows/daily-file-diet.lock.yml +++ b/.github/workflows/daily-file-diet.lock.yml @@ -115,17 +115,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, missing_tool, missing_data diff --git a/.github/workflows/daily-firewall-report.lock.yml b/.github/workflows/daily-firewall-report.lock.yml index ab84300c05..0f6afd3752 100644 --- a/.github/workflows/daily-firewall-report.lock.yml +++ b/.github/workflows/daily-firewall-report.lock.yml @@ -114,25 +114,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** + Tools: create_discussion, upload_asset, missing_tool, missing_data - To create a discussion, use the create_discussion tool from safeoutputs. - - **Uploading Assets** - - To upload files as URL-addressable assets: - 1. Use the upload_asset tool from safeoutputs. - 2. Provide the path to the file you want to upload. - 3. The tool will copy the file to a staging area and return a GitHub raw content URL. - 4. Assets are uploaded to an orphaned git branch after workflow completion. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). diff --git a/.github/workflows/daily-issues-report.lock.yml b/.github/workflows/daily-issues-report.lock.yml index 0e5940ff03..20c213ea91 100644 --- a/.github/workflows/daily-issues-report.lock.yml +++ b/.github/workflows/daily-issues-report.lock.yml @@ -119,29 +119,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** + Tools: create_discussion, close_discussion, upload_asset, missing_tool, missing_data - To create a discussion, use the create_discussion tool from safeoutputs. - - **Closing a Discussion** - - To close a discussion, use the close_discussion tool from safeoutputs. - - **Uploading Assets** - - To upload files as URL-addressable assets: - 1. Use the upload_asset tool from safeoutputs. - 2. Provide the path to the file you want to upload. - 3. The tool will copy the file to a staging area and return a GitHub raw content URL. - 4. Assets are uploaded to an orphaned git branch after workflow completion. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). diff --git a/.github/workflows/daily-malicious-code-scan.lock.yml b/.github/workflows/daily-malicious-code-scan.lock.yml index cc8bab1f54..5251029b0e 100644 --- a/.github/workflows/daily-malicious-code-scan.lock.yml +++ b/.github/workflows/daily-malicious-code-scan.lock.yml @@ -112,17 +112,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Code Scanning Alert** - - To create a code scanning alert, use the create_code_scanning_alert tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_code_scanning_alert, missing_tool, missing_data diff --git a/.github/workflows/daily-mcp-concurrency-analysis.lock.yml b/.github/workflows/daily-mcp-concurrency-analysis.lock.yml index 4053e049f3..fc4ef7cd73 100644 --- a/.github/workflows/daily-mcp-concurrency-analysis.lock.yml +++ b/.github/workflows/daily-mcp-concurrency-analysis.lock.yml @@ -113,21 +113,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Creating an Agent Session** - - To create a GitHub Copilot agent session, use the create_agent_session tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, create_agent_session, missing_tool, missing_data diff --git a/.github/workflows/daily-multi-device-docs-tester.lock.yml b/.github/workflows/daily-multi-device-docs-tester.lock.yml index e3de8f71ce..d3acf9cb8b 100644 --- a/.github/workflows/daily-multi-device-docs-tester.lock.yml +++ b/.github/workflows/daily-multi-device-docs-tester.lock.yml @@ -120,25 +120,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** + Tools: create_issue, upload_asset, missing_tool, missing_data - To create an issue, use the create_issue tool from safeoutputs. - - **Uploading Assets** - - To upload files as URL-addressable assets: - 1. Use the upload_asset tool from safeoutputs. - 2. Provide the path to the file you want to upload. - 3. The tool will copy the file to a staging area and return a GitHub raw content URL. - 4. Assets are uploaded to an orphaned git branch after workflow completion. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). diff --git a/.github/workflows/daily-news.lock.yml b/.github/workflows/daily-news.lock.yml index f85bccca69..1d93558859 100644 --- a/.github/workflows/daily-news.lock.yml +++ b/.github/workflows/daily-news.lock.yml @@ -117,25 +117,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** + Tools: create_discussion, upload_asset, missing_tool, missing_data - To create a discussion, use the create_discussion tool from safeoutputs. - - **Uploading Assets** - - To upload files as URL-addressable assets: - 1. Use the upload_asset tool from safeoutputs. - 2. Provide the path to the file you want to upload. - 3. The tool will copy the file to a staging area and return a GitHub raw content URL. - 4. Assets are uploaded to an orphaned git branch after workflow completion. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). diff --git a/.github/workflows/daily-observability-report.lock.yml b/.github/workflows/daily-observability-report.lock.yml index d8449417a7..9458bd9846 100644 --- a/.github/workflows/daily-observability-report.lock.yml +++ b/.github/workflows/daily-observability-report.lock.yml @@ -114,21 +114,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Closing a Discussion** - - To close a discussion, use the close_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, close_discussion, missing_tool, missing_data diff --git a/.github/workflows/daily-performance-summary.lock.yml b/.github/workflows/daily-performance-summary.lock.yml index 1907f34087..f89eb23bd7 100644 --- a/.github/workflows/daily-performance-summary.lock.yml +++ b/.github/workflows/daily-performance-summary.lock.yml @@ -115,29 +115,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** + Tools: create_discussion, close_discussion, upload_asset, missing_tool, missing_data - To create a discussion, use the create_discussion tool from safeoutputs. - - **Closing a Discussion** - - To close a discussion, use the close_discussion tool from safeoutputs. - - **Uploading Assets** - - To upload files as URL-addressable assets: - 1. Use the upload_asset tool from safeoutputs. - 2. Provide the path to the file you want to upload. - 3. The tool will copy the file to a staging area and return a GitHub raw content URL. - 4. Assets are uploaded to an orphaned git branch after workflow completion. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). diff --git a/.github/workflows/daily-regulatory.lock.yml b/.github/workflows/daily-regulatory.lock.yml index c1ace42c61..33a9b7ff41 100644 --- a/.github/workflows/daily-regulatory.lock.yml +++ b/.github/workflows/daily-regulatory.lock.yml @@ -113,21 +113,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Closing a Discussion** - - To close a discussion, use the close_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, close_discussion, missing_tool, missing_data diff --git a/.github/workflows/daily-rendering-scripts-verifier.lock.yml b/.github/workflows/daily-rendering-scripts-verifier.lock.yml index 02d87ff968..1353c66d5c 100644 --- a/.github/workflows/daily-rendering-scripts-verifier.lock.yml +++ b/.github/workflows/daily-rendering-scripts-verifier.lock.yml @@ -116,22 +116,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Pull Request** + Tools: create_pull_request, missing_tool, missing_data - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/daily-repo-chronicle.lock.yml b/.github/workflows/daily-repo-chronicle.lock.yml index 1daca32671..075c6bfa05 100644 --- a/.github/workflows/daily-repo-chronicle.lock.yml +++ b/.github/workflows/daily-repo-chronicle.lock.yml @@ -114,25 +114,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** + Tools: create_discussion, upload_asset, missing_tool, missing_data - To create a discussion, use the create_discussion tool from safeoutputs. - - **Uploading Assets** - - To upload files as URL-addressable assets: - 1. Use the upload_asset tool from safeoutputs. - 2. Provide the path to the file you want to upload. - 3. The tool will copy the file to a staging area and return a GitHub raw content URL. - 4. Assets are uploaded to an orphaned git branch after workflow completion. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). diff --git a/.github/workflows/daily-safe-output-optimizer.lock.yml b/.github/workflows/daily-safe-output-optimizer.lock.yml index 3d716d9388..8d67b4963d 100644 --- a/.github/workflows/daily-safe-output-optimizer.lock.yml +++ b/.github/workflows/daily-safe-output-optimizer.lock.yml @@ -117,17 +117,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, missing_tool, missing_data diff --git a/.github/workflows/daily-safe-outputs-conformance.lock.yml b/.github/workflows/daily-safe-outputs-conformance.lock.yml index 1495cbffc3..7aa0ed30b9 100644 --- a/.github/workflows/daily-safe-outputs-conformance.lock.yml +++ b/.github/workflows/daily-safe-outputs-conformance.lock.yml @@ -112,17 +112,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, missing_tool, missing_data diff --git a/.github/workflows/daily-secrets-analysis.lock.yml b/.github/workflows/daily-secrets-analysis.lock.yml index 1ebac25f9e..ca3b8facda 100644 --- a/.github/workflows/daily-secrets-analysis.lock.yml +++ b/.github/workflows/daily-secrets-analysis.lock.yml @@ -112,21 +112,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Closing a Discussion** - - To close a discussion, use the close_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, close_discussion, missing_tool, missing_data diff --git a/.github/workflows/daily-security-red-team.lock.yml b/.github/workflows/daily-security-red-team.lock.yml index ce16466d7a..61605d4b7a 100644 --- a/.github/workflows/daily-security-red-team.lock.yml +++ b/.github/workflows/daily-security-red-team.lock.yml @@ -113,17 +113,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, missing_tool, missing_data diff --git a/.github/workflows/daily-semgrep-scan.lock.yml b/.github/workflows/daily-semgrep-scan.lock.yml index 24c26b2793..8a8e913ece 100644 --- a/.github/workflows/daily-semgrep-scan.lock.yml +++ b/.github/workflows/daily-semgrep-scan.lock.yml @@ -112,17 +112,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Code Scanning Alert** - - To create a code scanning alert, use the create_code_scanning_alert tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_code_scanning_alert, missing_tool, missing_data diff --git a/.github/workflows/daily-syntax-error-quality.lock.yml b/.github/workflows/daily-syntax-error-quality.lock.yml index 6828653dbc..72da1629f5 100644 --- a/.github/workflows/daily-syntax-error-quality.lock.yml +++ b/.github/workflows/daily-syntax-error-quality.lock.yml @@ -112,17 +112,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, missing_tool, missing_data diff --git a/.github/workflows/daily-team-evolution-insights.lock.yml b/.github/workflows/daily-team-evolution-insights.lock.yml index b40d2a7b86..1fd70d3730 100644 --- a/.github/workflows/daily-team-evolution-insights.lock.yml +++ b/.github/workflows/daily-team-evolution-insights.lock.yml @@ -112,17 +112,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, missing_tool, missing_data diff --git a/.github/workflows/daily-team-status.lock.yml b/.github/workflows/daily-team-status.lock.yml index 158bd11904..2fa71f0a7f 100644 --- a/.github/workflows/daily-team-status.lock.yml +++ b/.github/workflows/daily-team-status.lock.yml @@ -121,17 +121,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, missing_tool, missing_data diff --git a/.github/workflows/daily-testify-uber-super-expert.lock.yml b/.github/workflows/daily-testify-uber-super-expert.lock.yml index e401bd1dda..5e87bd1b6b 100644 --- a/.github/workflows/daily-testify-uber-super-expert.lock.yml +++ b/.github/workflows/daily-testify-uber-super-expert.lock.yml @@ -117,17 +117,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, missing_tool, missing_data diff --git a/.github/workflows/daily-workflow-updater.lock.yml b/.github/workflows/daily-workflow-updater.lock.yml index 2bc9e1884a..bfb80430da 100644 --- a/.github/workflows/daily-workflow-updater.lock.yml +++ b/.github/workflows/daily-workflow-updater.lock.yml @@ -108,22 +108,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Pull Request** + Tools: create_pull_request, missing_tool, missing_data - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/deep-report.lock.yml b/.github/workflows/deep-report.lock.yml index d70023dd3b..0b2ef30337 100644 --- a/.github/workflows/deep-report.lock.yml +++ b/.github/workflows/deep-report.lock.yml @@ -115,29 +115,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** + Tools: create_issue, create_discussion, upload_asset, missing_tool, missing_data - To create an issue, use the create_issue tool from safeoutputs. - - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Uploading Assets** - - To upload files as URL-addressable assets: - 1. Use the upload_asset tool from safeoutputs. - 2. Provide the path to the file you want to upload. - 3. The tool will copy the file to a staging area and return a GitHub raw content URL. - 4. Assets are uploaded to an orphaned git branch after workflow completion. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). diff --git a/.github/workflows/delight.lock.yml b/.github/workflows/delight.lock.yml index 9d80028bc3..326889d3d3 100644 --- a/.github/workflows/delight.lock.yml +++ b/.github/workflows/delight.lock.yml @@ -114,21 +114,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, create_discussion, missing_tool, missing_data diff --git a/.github/workflows/dependabot-burner.lock.yml b/.github/workflows/dependabot-burner.lock.yml index 616470a6ae..ef554c6293 100644 --- a/.github/workflows/dependabot-burner.lock.yml +++ b/.github/workflows/dependabot-burner.lock.yml @@ -109,17 +109,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, missing_tool, missing_data diff --git a/.github/workflows/dependabot-go-checker.lock.yml b/.github/workflows/dependabot-go-checker.lock.yml index c6002ba2ff..ad412daf0b 100644 --- a/.github/workflows/dependabot-go-checker.lock.yml +++ b/.github/workflows/dependabot-go-checker.lock.yml @@ -107,21 +107,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Closing an Issue** - - To close an issue, use the close_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, close_issue, missing_tool, missing_data diff --git a/.github/workflows/dev-hawk.lock.yml b/.github/workflows/dev-hawk.lock.yml index 18773488ec..bcf5261896 100644 --- a/.github/workflows/dev-hawk.lock.yml +++ b/.github/workflows/dev-hawk.lock.yml @@ -124,17 +124,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** - - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: add_comment, missing_tool, missing_data diff --git a/.github/workflows/dev.lock.yml b/.github/workflows/dev.lock.yml index 82cfc68b1b..c60d2661d2 100644 --- a/.github/workflows/dev.lock.yml +++ b/.github/workflows/dev.lock.yml @@ -107,17 +107,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, missing_tool, missing_data diff --git a/.github/workflows/developer-docs-consolidator.lock.yml b/.github/workflows/developer-docs-consolidator.lock.yml index 9fb9a53575..adceb3b374 100644 --- a/.github/workflows/developer-docs-consolidator.lock.yml +++ b/.github/workflows/developer-docs-consolidator.lock.yml @@ -113,26 +113,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** + Tools: create_discussion, create_pull_request, missing_tool, missing_data - To create a discussion, use the create_discussion tool from safeoutputs. - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/dictation-prompt.lock.yml b/.github/workflows/dictation-prompt.lock.yml index b3944965de..7f734bacff 100644 --- a/.github/workflows/dictation-prompt.lock.yml +++ b/.github/workflows/dictation-prompt.lock.yml @@ -111,22 +111,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Pull Request** + Tools: create_pull_request, missing_tool, missing_data - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/discussion-task-miner.lock.yml b/.github/workflows/discussion-task-miner.lock.yml index 0f4bc8d304..3a1f4cc22a 100644 --- a/.github/workflows/discussion-task-miner.lock.yml +++ b/.github/workflows/discussion-task-miner.lock.yml @@ -114,21 +114,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** - - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: add_comment, create_issue, missing_tool, missing_data diff --git a/.github/workflows/docs-noob-tester.lock.yml b/.github/workflows/docs-noob-tester.lock.yml index 010b54dca0..7b7db54205 100644 --- a/.github/workflows/docs-noob-tester.lock.yml +++ b/.github/workflows/docs-noob-tester.lock.yml @@ -113,25 +113,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** + Tools: create_discussion, upload_asset, missing_tool, missing_data - To create a discussion, use the create_discussion tool from safeoutputs. - - **Uploading Assets** - - To upload files as URL-addressable assets: - 1. Use the upload_asset tool from safeoutputs. - 2. Provide the path to the file you want to upload. - 3. The tool will copy the file to a staging area and return a GitHub raw content URL. - 4. Assets are uploaded to an orphaned git branch after workflow completion. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). diff --git a/.github/workflows/draft-pr-cleanup.lock.yml b/.github/workflows/draft-pr-cleanup.lock.yml index ed119ee0ca..498cf2e318 100644 --- a/.github/workflows/draft-pr-cleanup.lock.yml +++ b/.github/workflows/draft-pr-cleanup.lock.yml @@ -108,25 +108,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** - - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Closing a Pull Request** - - To close a pull request, use the close_pull_request tool from safeoutputs. - - **Adding Labels to Issues or Pull Requests** - - To add labels to an issue or pull request, use the add_labels tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: add_comment, close_pull_request, add_labels, missing_tool, missing_data diff --git a/.github/workflows/duplicate-code-detector.lock.yml b/.github/workflows/duplicate-code-detector.lock.yml index 56064f5888..761ab1c919 100644 --- a/.github/workflows/duplicate-code-detector.lock.yml +++ b/.github/workflows/duplicate-code-detector.lock.yml @@ -109,17 +109,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, missing_tool, missing_data diff --git a/.github/workflows/example-workflow-analyzer.lock.yml b/.github/workflows/example-workflow-analyzer.lock.yml index 7b4a3e3880..cd65c8e591 100644 --- a/.github/workflows/example-workflow-analyzer.lock.yml +++ b/.github/workflows/example-workflow-analyzer.lock.yml @@ -112,17 +112,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, missing_tool, missing_data diff --git a/.github/workflows/firewall-escape.lock.yml b/.github/workflows/firewall-escape.lock.yml index aab0606ba2..0b40490da4 100644 --- a/.github/workflows/firewall-escape.lock.yml +++ b/.github/workflows/firewall-escape.lock.yml @@ -132,17 +132,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, missing_tool, missing_data diff --git a/.github/workflows/functional-pragmatist.lock.yml b/.github/workflows/functional-pragmatist.lock.yml index 55716ea5fa..ae83545c13 100644 --- a/.github/workflows/functional-pragmatist.lock.yml +++ b/.github/workflows/functional-pragmatist.lock.yml @@ -111,22 +111,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Pull Request** + Tools: create_pull_request, missing_tool, missing_data - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/github-mcp-structural-analysis.lock.yml b/.github/workflows/github-mcp-structural-analysis.lock.yml index 5639505c09..898c03a0cf 100644 --- a/.github/workflows/github-mcp-structural-analysis.lock.yml +++ b/.github/workflows/github-mcp-structural-analysis.lock.yml @@ -113,25 +113,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** + Tools: create_discussion, upload_asset, missing_tool, missing_data - To create a discussion, use the create_discussion tool from safeoutputs. - - **Uploading Assets** - - To upload files as URL-addressable assets: - 1. Use the upload_asset tool from safeoutputs. - 2. Provide the path to the file you want to upload. - 3. The tool will copy the file to a staging area and return a GitHub raw content URL. - 4. Assets are uploaded to an orphaned git branch after workflow completion. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). diff --git a/.github/workflows/github-mcp-tools-report.lock.yml b/.github/workflows/github-mcp-tools-report.lock.yml index 3293ee8c65..0f1256b971 100644 --- a/.github/workflows/github-mcp-tools-report.lock.yml +++ b/.github/workflows/github-mcp-tools-report.lock.yml @@ -113,26 +113,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** + Tools: create_discussion, create_pull_request, missing_tool, missing_data - To create a discussion, use the create_discussion tool from safeoutputs. - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/github-remote-mcp-auth-test.lock.yml b/.github/workflows/github-remote-mcp-auth-test.lock.yml index cf11b13642..1f13745ade 100644 --- a/.github/workflows/github-remote-mcp-auth-test.lock.yml +++ b/.github/workflows/github-remote-mcp-auth-test.lock.yml @@ -109,17 +109,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, missing_tool, missing_data diff --git a/.github/workflows/glossary-maintainer.lock.yml b/.github/workflows/glossary-maintainer.lock.yml index 1814818199..b0977106d6 100644 --- a/.github/workflows/glossary-maintainer.lock.yml +++ b/.github/workflows/glossary-maintainer.lock.yml @@ -113,22 +113,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Pull Request** + Tools: create_pull_request, missing_tool, missing_data - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/go-fan.lock.yml b/.github/workflows/go-fan.lock.yml index efce769752..3b436b9a1f 100644 --- a/.github/workflows/go-fan.lock.yml +++ b/.github/workflows/go-fan.lock.yml @@ -112,17 +112,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, missing_tool, missing_data diff --git a/.github/workflows/go-logger.lock.yml b/.github/workflows/go-logger.lock.yml index ce08e4d804..7168088577 100644 --- a/.github/workflows/go-logger.lock.yml +++ b/.github/workflows/go-logger.lock.yml @@ -113,22 +113,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Pull Request** + Tools: create_pull_request, missing_tool, missing_data - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/go-pattern-detector.lock.yml b/.github/workflows/go-pattern-detector.lock.yml index 25e6893ff5..9b804a6b61 100644 --- a/.github/workflows/go-pattern-detector.lock.yml +++ b/.github/workflows/go-pattern-detector.lock.yml @@ -112,17 +112,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, missing_tool, missing_data diff --git a/.github/workflows/gpclean.lock.yml b/.github/workflows/gpclean.lock.yml index 1beae9539c..a9a668ab43 100644 --- a/.github/workflows/gpclean.lock.yml +++ b/.github/workflows/gpclean.lock.yml @@ -109,17 +109,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, missing_tool, missing_data diff --git a/.github/workflows/grumpy-reviewer.lock.yml b/.github/workflows/grumpy-reviewer.lock.yml index 72095495c8..340c407cc6 100644 --- a/.github/workflows/grumpy-reviewer.lock.yml +++ b/.github/workflows/grumpy-reviewer.lock.yml @@ -136,21 +136,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Pull Request Review Comment** - - To create a pull request review comment, use the create_pull_request_review_comment tool from safeoutputs. - - **Submitting a Pull Request Review** - - To submit a pull request review (APPROVE, REQUEST_CHANGES, or COMMENT), use the submit_pull_request_review tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_pull_request_review_comment, submit_pull_request_review, missing_tool, missing_data diff --git a/.github/workflows/hourly-ci-cleaner.lock.yml b/.github/workflows/hourly-ci-cleaner.lock.yml index 5b5e0dc73a..640fcddbd1 100644 --- a/.github/workflows/hourly-ci-cleaner.lock.yml +++ b/.github/workflows/hourly-ci-cleaner.lock.yml @@ -116,22 +116,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Pull Request** + Tools: create_pull_request, missing_tool, missing_data - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/instructions-janitor.lock.yml b/.github/workflows/instructions-janitor.lock.yml index 8a1a188ae8..5d21371446 100644 --- a/.github/workflows/instructions-janitor.lock.yml +++ b/.github/workflows/instructions-janitor.lock.yml @@ -109,22 +109,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Pull Request** + Tools: create_pull_request, missing_tool, missing_data - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/issue-arborist.lock.yml b/.github/workflows/issue-arborist.lock.yml index 412de9c6c4..886e229267 100644 --- a/.github/workflows/issue-arborist.lock.yml +++ b/.github/workflows/issue-arborist.lock.yml @@ -112,25 +112,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Linking a Sub-Issue** - - To link an issue as a sub-issue of another issue, use the link_sub_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, create_discussion, link_sub_issue, missing_tool, missing_data diff --git a/.github/workflows/issue-monster.lock.yml b/.github/workflows/issue-monster.lock.yml index 1c43859363..06893733ea 100644 --- a/.github/workflows/issue-monster.lock.yml +++ b/.github/workflows/issue-monster.lock.yml @@ -119,21 +119,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** - - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Assigning to an Agent** - - To assign an issue or pull request to a GitHub Copilot agent, use the assign_to_agent tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: add_comment, assign_to_agent, missing_tool, missing_data diff --git a/.github/workflows/issue-triage-agent.lock.yml b/.github/workflows/issue-triage-agent.lock.yml index 05802d0943..4881caca7a 100644 --- a/.github/workflows/issue-triage-agent.lock.yml +++ b/.github/workflows/issue-triage-agent.lock.yml @@ -102,21 +102,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** - - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Adding Labels to Issues or Pull Requests** - - To add labels to an issue or pull request, use the add_labels tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: add_comment, add_labels, missing_tool, missing_data diff --git a/.github/workflows/jsweep.lock.yml b/.github/workflows/jsweep.lock.yml index 26686566e0..b830c94518 100644 --- a/.github/workflows/jsweep.lock.yml +++ b/.github/workflows/jsweep.lock.yml @@ -109,22 +109,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Pull Request** + Tools: create_pull_request, missing_tool, missing_data - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/layout-spec-maintainer.lock.yml b/.github/workflows/layout-spec-maintainer.lock.yml index dd37502d26..1e48863841 100644 --- a/.github/workflows/layout-spec-maintainer.lock.yml +++ b/.github/workflows/layout-spec-maintainer.lock.yml @@ -109,22 +109,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Pull Request** + Tools: create_pull_request, missing_tool, missing_data - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/lockfile-stats.lock.yml b/.github/workflows/lockfile-stats.lock.yml index a3002fbfac..a577879e4a 100644 --- a/.github/workflows/lockfile-stats.lock.yml +++ b/.github/workflows/lockfile-stats.lock.yml @@ -113,17 +113,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, missing_tool, missing_data diff --git a/.github/workflows/mcp-inspector.lock.yml b/.github/workflows/mcp-inspector.lock.yml index f78af7869d..93dbc4701d 100644 --- a/.github/workflows/mcp-inspector.lock.yml +++ b/.github/workflows/mcp-inspector.lock.yml @@ -127,17 +127,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, missing_tool, missing_data diff --git a/.github/workflows/mergefest.lock.yml b/.github/workflows/mergefest.lock.yml index 85cb33399d..64dfcb7304 100644 --- a/.github/workflows/mergefest.lock.yml +++ b/.github/workflows/mergefest.lock.yml @@ -129,20 +129,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Pushing Changes to a Pull Request Branch** + Tools: push_to_pull_request_branch, missing_tool, missing_data - To push changes to the branch of a pull request: - 1. Make any file changes directly in the working directory. - 2. Add and commit your changes to the local copy of the pull request branch. Be careful to add exactly the files you intend, and verify you haven't deleted or changed any files you didn't intend to. - 3. Push the branch to the repo by using the push_to_pull_request_branch tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + push_to_pull_request_branch: commit changes locally (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/notion-issue-summary.lock.yml b/.github/workflows/notion-issue-summary.lock.yml index 4bb0139dbe..e8e24363ac 100644 --- a/.github/workflows/notion-issue-summary.lock.yml +++ b/.github/workflows/notion-issue-summary.lock.yml @@ -115,13 +115,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: missing_tool, missing_data diff --git a/.github/workflows/org-health-report.lock.yml b/.github/workflows/org-health-report.lock.yml index 9937a83731..0013e561da 100644 --- a/.github/workflows/org-health-report.lock.yml +++ b/.github/workflows/org-health-report.lock.yml @@ -115,25 +115,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** + Tools: create_discussion, upload_asset, missing_tool, missing_data - To create a discussion, use the create_discussion tool from safeoutputs. - - **Uploading Assets** - - To upload files as URL-addressable assets: - 1. Use the upload_asset tool from safeoutputs. - 2. Provide the path to the file you want to upload. - 3. The tool will copy the file to a staging area and return a GitHub raw content URL. - 4. Assets are uploaded to an orphaned git branch after workflow completion. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). diff --git a/.github/workflows/pdf-summary.lock.yml b/.github/workflows/pdf-summary.lock.yml index dd96ba6a71..45b90a2c3e 100644 --- a/.github/workflows/pdf-summary.lock.yml +++ b/.github/workflows/pdf-summary.lock.yml @@ -157,21 +157,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** - - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: add_comment, create_discussion, missing_tool, missing_data diff --git a/.github/workflows/plan.lock.yml b/.github/workflows/plan.lock.yml index bdad701318..8c7303e75f 100644 --- a/.github/workflows/plan.lock.yml +++ b/.github/workflows/plan.lock.yml @@ -135,21 +135,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Closing a Discussion** - - To close a discussion, use the close_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, close_discussion, missing_tool, missing_data diff --git a/.github/workflows/poem-bot.lock.yml b/.github/workflows/poem-bot.lock.yml index 1a92236139..23dba46e28 100644 --- a/.github/workflows/poem-bot.lock.yml +++ b/.github/workflows/poem-bot.lock.yml @@ -147,73 +147,13 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** + Tools: add_comment, create_issue, update_issue, create_discussion, create_agent_session, create_pull_request, close_pull_request, create_pull_request_review_comment, add_labels, push_to_pull_request_branch, upload_asset, link_sub_issue, missing_tool, missing_data - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. - **Creating an Issue** + push_to_pull_request_branch: commit changes locally (do not push), then call this tool from safeoutputs. - To create an issue, use the create_issue tool from safeoutputs. - - **Updating an Issue** - - To update an issue, use the update_issue tool from safeoutputs. - - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Creating an Agent Session** - - To create a GitHub Copilot agent session, use the create_agent_session tool from safeoutputs. - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Closing a Pull Request** - - To close a pull request, use the close_pull_request tool from safeoutputs. - - **Creating a Pull Request Review Comment** - - To create a pull request review comment, use the create_pull_request_review_comment tool from safeoutputs. - - **Adding Labels to Issues or Pull Requests** - - To add labels to an issue or pull request, use the add_labels tool from safeoutputs. - - **Pushing Changes to a Pull Request Branch** - - To push changes to the branch of a pull request: - 1. Make any file changes directly in the working directory. - 2. Add and commit your changes to the local copy of the pull request branch. Be careful to add exactly the files you intend, and verify you haven't deleted or changed any files you didn't intend to. - 3. Push the branch to the repo by using the push_to_pull_request_branch tool from safeoutputs. - - **Uploading Assets** - - To upload files as URL-addressable assets: - 1. Use the upload_asset tool from safeoutputs. - 2. Provide the path to the file you want to upload. - 3. The tool will copy the file to a staging area and return a GitHub raw content URL. - 4. Assets are uploaded to an orphaned git branch after workflow completion. - - **Linking a Sub-Issue** - - To link an issue as a sub-issue of another issue, use the link_sub_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). diff --git a/.github/workflows/portfolio-analyst.lock.yml b/.github/workflows/portfolio-analyst.lock.yml index db44e6af39..538e5050bb 100644 --- a/.github/workflows/portfolio-analyst.lock.yml +++ b/.github/workflows/portfolio-analyst.lock.yml @@ -115,25 +115,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** + Tools: create_discussion, upload_asset, missing_tool, missing_data - To create a discussion, use the create_discussion tool from safeoutputs. - - **Uploading Assets** - - To upload files as URL-addressable assets: - 1. Use the upload_asset tool from safeoutputs. - 2. Provide the path to the file you want to upload. - 3. The tool will copy the file to a staging area and return a GitHub raw content URL. - 4. Assets are uploaded to an orphaned git branch after workflow completion. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). diff --git a/.github/workflows/pr-nitpick-reviewer.lock.yml b/.github/workflows/pr-nitpick-reviewer.lock.yml index 71ebf0e4a0..7410b73134 100644 --- a/.github/workflows/pr-nitpick-reviewer.lock.yml +++ b/.github/workflows/pr-nitpick-reviewer.lock.yml @@ -164,25 +164,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Creating a Pull Request Review Comment** - - To create a pull request review comment, use the create_pull_request_review_comment tool from safeoutputs. - - **Submitting a Pull Request Review** - - To submit a pull request review (APPROVE, REQUEST_CHANGES, or COMMENT), use the submit_pull_request_review tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, create_pull_request_review_comment, submit_pull_request_review, missing_tool, missing_data diff --git a/.github/workflows/pr-triage-agent.lock.yml b/.github/workflows/pr-triage-agent.lock.yml index 04f93664f6..c68012f607 100644 --- a/.github/workflows/pr-triage-agent.lock.yml +++ b/.github/workflows/pr-triage-agent.lock.yml @@ -108,25 +108,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** - - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Adding Labels to Issues or Pull Requests** - - To add labels to an issue or pull request, use the add_labels tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: add_comment, create_issue, add_labels, missing_tool, missing_data diff --git a/.github/workflows/prompt-clustering-analysis.lock.yml b/.github/workflows/prompt-clustering-analysis.lock.yml index f725d8f08d..554101f0ee 100644 --- a/.github/workflows/prompt-clustering-analysis.lock.yml +++ b/.github/workflows/prompt-clustering-analysis.lock.yml @@ -118,17 +118,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, missing_tool, missing_data diff --git a/.github/workflows/python-data-charts.lock.yml b/.github/workflows/python-data-charts.lock.yml index 83f3cb564a..b9f0d5740e 100644 --- a/.github/workflows/python-data-charts.lock.yml +++ b/.github/workflows/python-data-charts.lock.yml @@ -112,25 +112,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** + Tools: create_discussion, upload_asset, missing_tool, missing_data - To create a discussion, use the create_discussion tool from safeoutputs. - - **Uploading Assets** - - To upload files as URL-addressable assets: - 1. Use the upload_asset tool from safeoutputs. - 2. Provide the path to the file you want to upload. - 3. The tool will copy the file to a staging area and return a GitHub raw content URL. - 4. Assets are uploaded to an orphaned git branch after workflow completion. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). diff --git a/.github/workflows/q.lock.yml b/.github/workflows/q.lock.yml index e8f7333de9..397959c135 100644 --- a/.github/workflows/q.lock.yml +++ b/.github/workflows/q.lock.yml @@ -169,26 +169,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** + Tools: add_comment, create_pull_request, missing_tool, missing_data - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/refiner.lock.yml b/.github/workflows/refiner.lock.yml index b0a28053fe..ba86c3996c 100644 --- a/.github/workflows/refiner.lock.yml +++ b/.github/workflows/refiner.lock.yml @@ -133,26 +133,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** + Tools: add_comment, create_pull_request, missing_tool, missing_data - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/release.lock.yml b/.github/workflows/release.lock.yml index 7259d9fe38..fa03f977d3 100644 --- a/.github/workflows/release.lock.yml +++ b/.github/workflows/release.lock.yml @@ -119,17 +119,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Updating a Release** - - To update a GitHub release description, use the update_release tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: update_release, missing_tool, missing_data diff --git a/.github/workflows/repo-audit-analyzer.lock.yml b/.github/workflows/repo-audit-analyzer.lock.yml index ef0c477fd4..2470ffc05f 100644 --- a/.github/workflows/repo-audit-analyzer.lock.yml +++ b/.github/workflows/repo-audit-analyzer.lock.yml @@ -117,17 +117,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, missing_tool, missing_data diff --git a/.github/workflows/repo-tree-map.lock.yml b/.github/workflows/repo-tree-map.lock.yml index f487e26e1b..060b6e0043 100644 --- a/.github/workflows/repo-tree-map.lock.yml +++ b/.github/workflows/repo-tree-map.lock.yml @@ -112,17 +112,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, missing_tool, missing_data diff --git a/.github/workflows/repository-quality-improver.lock.yml b/.github/workflows/repository-quality-improver.lock.yml index a0a3cef9c6..56fdf3c574 100644 --- a/.github/workflows/repository-quality-improver.lock.yml +++ b/.github/workflows/repository-quality-improver.lock.yml @@ -112,17 +112,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, missing_tool, missing_data diff --git a/.github/workflows/research.lock.yml b/.github/workflows/research.lock.yml index 6c11eeb3e4..096efe011f 100644 --- a/.github/workflows/research.lock.yml +++ b/.github/workflows/research.lock.yml @@ -116,17 +116,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, missing_tool, missing_data diff --git a/.github/workflows/safe-output-health.lock.yml b/.github/workflows/safe-output-health.lock.yml index c70dd4762e..e4f4547c39 100644 --- a/.github/workflows/safe-output-health.lock.yml +++ b/.github/workflows/safe-output-health.lock.yml @@ -114,17 +114,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, missing_tool, missing_data diff --git a/.github/workflows/schema-consistency-checker.lock.yml b/.github/workflows/schema-consistency-checker.lock.yml index 0f84f38827..2134eea16a 100644 --- a/.github/workflows/schema-consistency-checker.lock.yml +++ b/.github/workflows/schema-consistency-checker.lock.yml @@ -113,17 +113,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, missing_tool, missing_data diff --git a/.github/workflows/scout.lock.yml b/.github/workflows/scout.lock.yml index 51b66376f4..da23f570f4 100644 --- a/.github/workflows/scout.lock.yml +++ b/.github/workflows/scout.lock.yml @@ -194,17 +194,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** - - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: add_comment, missing_tool, missing_data diff --git a/.github/workflows/security-compliance.lock.yml b/.github/workflows/security-compliance.lock.yml index 5fe55d55b6..2fb5c9435b 100644 --- a/.github/workflows/security-compliance.lock.yml +++ b/.github/workflows/security-compliance.lock.yml @@ -133,17 +133,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, missing_tool, missing_data diff --git a/.github/workflows/security-review.lock.yml b/.github/workflows/security-review.lock.yml index ba07d2c2a4..c67f60302a 100644 --- a/.github/workflows/security-review.lock.yml +++ b/.github/workflows/security-review.lock.yml @@ -136,21 +136,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Pull Request Review Comment** - - To create a pull request review comment, use the create_pull_request_review_comment tool from safeoutputs. - - **Submitting a Pull Request Review** - - To submit a pull request review (APPROVE, REQUEST_CHANGES, or COMMENT), use the submit_pull_request_review tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_pull_request_review_comment, submit_pull_request_review, missing_tool, missing_data diff --git a/.github/workflows/semantic-function-refactor.lock.yml b/.github/workflows/semantic-function-refactor.lock.yml index bfc8e3e117..e9f4ea31a4 100644 --- a/.github/workflows/semantic-function-refactor.lock.yml +++ b/.github/workflows/semantic-function-refactor.lock.yml @@ -112,21 +112,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Closing an Issue** - - To close an issue, use the close_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, close_issue, missing_tool, missing_data diff --git a/.github/workflows/sergo.lock.yml b/.github/workflows/sergo.lock.yml index 87c0398a8b..755264df16 100644 --- a/.github/workflows/sergo.lock.yml +++ b/.github/workflows/sergo.lock.yml @@ -113,17 +113,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, missing_tool, missing_data diff --git a/.github/workflows/slide-deck-maintainer.lock.yml b/.github/workflows/slide-deck-maintainer.lock.yml index 403caf539d..21052311c6 100644 --- a/.github/workflows/slide-deck-maintainer.lock.yml +++ b/.github/workflows/slide-deck-maintainer.lock.yml @@ -119,22 +119,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Pull Request** + Tools: create_pull_request, missing_tool, missing_data - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/smoke-agent.lock.yml b/.github/workflows/smoke-agent.lock.yml index 39631175e6..f845238f89 100644 --- a/.github/workflows/smoke-agent.lock.yml +++ b/.github/workflows/smoke-agent.lock.yml @@ -141,21 +141,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** - - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Assigning to an Agent** - - To assign an issue or pull request to a GitHub Copilot agent, use the assign_to_agent tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: add_comment, assign_to_agent, missing_tool, missing_data diff --git a/.github/workflows/smoke-claude.lock.yml b/.github/workflows/smoke-claude.lock.yml index 8e0c0d5d1c..6b3beadb09 100644 --- a/.github/workflows/smoke-claude.lock.yml +++ b/.github/workflows/smoke-claude.lock.yml @@ -161,56 +161,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** + Tools: add_comment, create_issue, close_pull_request, update_pull_request, create_pull_request_review_comment, submit_pull_request_review, resolve_pull_request_review_thread, add_labels, add_reviewer, push_to_pull_request_branch, missing_tool, missing_data - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Closing a Pull Request** - - To close a pull request, use the close_pull_request tool from safeoutputs. - - **Updating a Pull Request** - - To update a pull request title or body, use the update_pull_request tool from safeoutputs. - - **Creating a Pull Request Review Comment** - - To create a pull request review comment, use the create_pull_request_review_comment tool from safeoutputs. - - **Submitting a Pull Request Review** - - To submit a pull request review (APPROVE, REQUEST_CHANGES, or COMMENT), use the submit_pull_request_review tool from safeoutputs. - - **Resolving a Pull Request Review Thread** - - To resolve a review thread on a pull request, use the resolve_pull_request_review_thread tool from safeoutputs. - - **Adding Labels to Issues or Pull Requests** - - To add labels to an issue or pull request, use the add_labels tool from safeoutputs. - - **Adding a Reviewer to a Pull Request** - - To add a reviewer to a pull request, use the add_reviewer tool from safeoutputs. - - **Pushing Changes to a Pull Request Branch** - - To push changes to the branch of a pull request: - 1. Make any file changes directly in the working directory. - 2. Add and commit your changes to the local copy of the pull request branch. Be careful to add exactly the files you intend, and verify you haven't deleted or changed any files you didn't intend to. - 3. Push the branch to the repo by using the push_to_pull_request_branch tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + push_to_pull_request_branch: commit changes locally (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/smoke-codex.lock.yml b/.github/workflows/smoke-codex.lock.yml index 58de44dc1b..98c003d7ef 100644 --- a/.github/workflows/smoke-codex.lock.yml +++ b/.github/workflows/smoke-codex.lock.yml @@ -153,37 +153,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** - - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Adding Labels to Issues or Pull Requests** - - To add labels to an issue or pull request, use the add_labels tool from safeoutputs. - - **Removing Labels from Issues or Pull Requests** - - To remove labels from an issue or pull request, use the remove_labels tool from safeoutputs. - - **Unassigning from a User** - - To remove a user assignee from an issue or pull request, use the unassign_from_user tool from safeoutputs. - - **Hiding a Comment** - - To hide a comment, use the hide_comment tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: add_comment, create_issue, add_labels, remove_labels, unassign_from_user, hide_comment, missing_tool, missing_data diff --git a/.github/workflows/smoke-copilot-arm.lock.yml b/.github/workflows/smoke-copilot-arm.lock.yml index 102dceaf64..5671e18a69 100644 --- a/.github/workflows/smoke-copilot-arm.lock.yml +++ b/.github/workflows/smoke-copilot-arm.lock.yml @@ -153,45 +153,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** - - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Creating a Pull Request Review Comment** - - To create a pull request review comment, use the create_pull_request_review_comment tool from safeoutputs. - - **Submitting a Pull Request Review** - - To submit a pull request review (APPROVE, REQUEST_CHANGES, or COMMENT), use the submit_pull_request_review tool from safeoutputs. - - **Adding Labels to Issues or Pull Requests** - - To add labels to an issue or pull request, use the add_labels tool from safeoutputs. - - **Removing Labels from Issues or Pull Requests** - - To remove labels from an issue or pull request, use the remove_labels tool from safeoutputs. - - **Dispatching a Workflow** - - To dispatch a workflow_dispatch event to another workflow, use the dispatch_workflow tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: add_comment, create_issue, create_discussion, create_pull_request_review_comment, submit_pull_request_review, add_labels, remove_labels, dispatch_workflow, missing_tool, missing_data diff --git a/.github/workflows/smoke-copilot.lock.yml b/.github/workflows/smoke-copilot.lock.yml index cdb7ebd5f9..45390f2785 100644 --- a/.github/workflows/smoke-copilot.lock.yml +++ b/.github/workflows/smoke-copilot.lock.yml @@ -155,45 +155,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** - - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Creating a Pull Request Review Comment** - - To create a pull request review comment, use the create_pull_request_review_comment tool from safeoutputs. - - **Submitting a Pull Request Review** - - To submit a pull request review (APPROVE, REQUEST_CHANGES, or COMMENT), use the submit_pull_request_review tool from safeoutputs. - - **Adding Labels to Issues or Pull Requests** - - To add labels to an issue or pull request, use the add_labels tool from safeoutputs. - - **Removing Labels from Issues or Pull Requests** - - To remove labels from an issue or pull request, use the remove_labels tool from safeoutputs. - - **Dispatching a Workflow** - - To dispatch a workflow_dispatch event to another workflow, use the dispatch_workflow tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: add_comment, create_issue, create_discussion, create_pull_request_review_comment, submit_pull_request_review, add_labels, remove_labels, dispatch_workflow, missing_tool, missing_data diff --git a/.github/workflows/smoke-gemini.lock.yml b/.github/workflows/smoke-gemini.lock.yml index 3ae8224e8d..e9e19a9e84 100644 --- a/.github/workflows/smoke-gemini.lock.yml +++ b/.github/workflows/smoke-gemini.lock.yml @@ -152,25 +152,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** - - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Adding Labels to Issues or Pull Requests** - - To add labels to an issue or pull request, use the add_labels tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: add_comment, create_issue, add_labels, missing_tool, missing_data diff --git a/.github/workflows/smoke-multi-pr.lock.yml b/.github/workflows/smoke-multi-pr.lock.yml index 6f7404b6dd..32478aabb2 100644 --- a/.github/workflows/smoke-multi-pr.lock.yml +++ b/.github/workflows/smoke-multi-pr.lock.yml @@ -146,26 +146,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** + Tools: add_comment, create_pull_request, missing_tool, missing_data - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/smoke-project.lock.yml b/.github/workflows/smoke-project.lock.yml index fddb57ccce..f0599d495c 100644 --- a/.github/workflows/smoke-project.lock.yml +++ b/.github/workflows/smoke-project.lock.yml @@ -144,46 +144,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** + Tools: add_comment, create_issue, create_pull_request, add_labels, remove_labels, update_project, create_project_status_update, missing_tool, missing_data - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Adding Labels to Issues or Pull Requests** - - To add labels to an issue or pull request, use the add_labels tool from safeoutputs. - - **Removing Labels from Issues or Pull Requests** - - To remove labels from an issue or pull request, use the remove_labels tool from safeoutputs. - - **Updating a Project** - - To create, add items to, or update a project board, use the update_project tool from safeoutputs. - - **Creating a Project Status Update** - - To create a project status update, use the create_project_status_update tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/smoke-temporary-id.lock.yml b/.github/workflows/smoke-temporary-id.lock.yml index 982af6c6bd..3d0b461b3a 100644 --- a/.github/workflows/smoke-temporary-id.lock.yml +++ b/.github/workflows/smoke-temporary-id.lock.yml @@ -144,25 +144,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** - - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Linking a Sub-Issue** - - To link an issue as a sub-issue of another issue, use the link_sub_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: add_comment, create_issue, link_sub_issue, missing_tool, missing_data diff --git a/.github/workflows/smoke-test-tools.lock.yml b/.github/workflows/smoke-test-tools.lock.yml index 2f8eb2ae8e..fd2fde94aa 100644 --- a/.github/workflows/smoke-test-tools.lock.yml +++ b/.github/workflows/smoke-test-tools.lock.yml @@ -143,17 +143,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** - - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: add_comment, missing_tool, missing_data diff --git a/.github/workflows/stale-repo-identifier.lock.yml b/.github/workflows/stale-repo-identifier.lock.yml index 4d75b723b3..9851b14257 100644 --- a/.github/workflows/stale-repo-identifier.lock.yml +++ b/.github/workflows/stale-repo-identifier.lock.yml @@ -124,25 +124,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** + Tools: create_issue, upload_asset, missing_tool, missing_data - To create an issue, use the create_issue tool from safeoutputs. - - **Uploading Assets** - - To upload files as URL-addressable assets: - 1. Use the upload_asset tool from safeoutputs. - 2. Provide the path to the file you want to upload. - 3. The tool will copy the file to a staging area and return a GitHub raw content URL. - 4. Assets are uploaded to an orphaned git branch after workflow completion. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). diff --git a/.github/workflows/static-analysis-report.lock.yml b/.github/workflows/static-analysis-report.lock.yml index 1f96579081..7d0f0e9f49 100644 --- a/.github/workflows/static-analysis-report.lock.yml +++ b/.github/workflows/static-analysis-report.lock.yml @@ -113,17 +113,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, missing_tool, missing_data diff --git a/.github/workflows/step-name-alignment.lock.yml b/.github/workflows/step-name-alignment.lock.yml index a12c26f375..e2977a5df1 100644 --- a/.github/workflows/step-name-alignment.lock.yml +++ b/.github/workflows/step-name-alignment.lock.yml @@ -109,17 +109,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, missing_tool, missing_data diff --git a/.github/workflows/sub-issue-closer.lock.yml b/.github/workflows/sub-issue-closer.lock.yml index 721b3fccdb..0ed3ce91da 100644 --- a/.github/workflows/sub-issue-closer.lock.yml +++ b/.github/workflows/sub-issue-closer.lock.yml @@ -108,21 +108,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** - - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Updating an Issue** - - To update an issue, use the update_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: add_comment, update_issue, missing_tool, missing_data diff --git a/.github/workflows/super-linter.lock.yml b/.github/workflows/super-linter.lock.yml index 0f808d63c9..987bb90264 100644 --- a/.github/workflows/super-linter.lock.yml +++ b/.github/workflows/super-linter.lock.yml @@ -113,17 +113,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, missing_tool, missing_data diff --git a/.github/workflows/technical-doc-writer.lock.yml b/.github/workflows/technical-doc-writer.lock.yml index b2ba56651f..5654cfdf3a 100644 --- a/.github/workflows/technical-doc-writer.lock.yml +++ b/.github/workflows/technical-doc-writer.lock.yml @@ -117,34 +117,11 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** + Tools: add_comment, create_pull_request, upload_asset, missing_tool, missing_data - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Uploading Assets** - - To upload files as URL-addressable assets: - 1. Use the upload_asset tool from safeoutputs. - 2. Provide the path to the file you want to upload. - 3. The tool will copy the file to a staging area and return a GitHub raw content URL. - 4. Assets are uploaded to an orphaned git branch after workflow completion. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). diff --git a/.github/workflows/terminal-stylist.lock.yml b/.github/workflows/terminal-stylist.lock.yml index 80f3f9cf60..a1f548038c 100644 --- a/.github/workflows/terminal-stylist.lock.yml +++ b/.github/workflows/terminal-stylist.lock.yml @@ -108,17 +108,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, missing_tool, missing_data diff --git a/.github/workflows/test-create-pr-error-handling.lock.yml b/.github/workflows/test-create-pr-error-handling.lock.yml index 2d74cb7da0..fc91c4dc26 100644 --- a/.github/workflows/test-create-pr-error-handling.lock.yml +++ b/.github/workflows/test-create-pr-error-handling.lock.yml @@ -106,22 +106,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Pull Request** + Tools: create_pull_request, missing_tool, missing_data - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/test-dispatcher.lock.yml b/.github/workflows/test-dispatcher.lock.yml index 0b1a9ae816..50e890facf 100644 --- a/.github/workflows/test-dispatcher.lock.yml +++ b/.github/workflows/test-dispatcher.lock.yml @@ -104,17 +104,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Dispatching a Workflow** - - To dispatch a workflow_dispatch event to another workflow, use the dispatch_workflow tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: dispatch_workflow, missing_tool, missing_data diff --git a/.github/workflows/test-project-url-default.lock.yml b/.github/workflows/test-project-url-default.lock.yml index 1c443ea296..5fa2d1d91c 100644 --- a/.github/workflows/test-project-url-default.lock.yml +++ b/.github/workflows/test-project-url-default.lock.yml @@ -104,21 +104,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Updating a Project** - - To create, add items to, or update a project board, use the update_project tool from safeoutputs. - - **Creating a Project Status Update** - - To create a project status update, use the create_project_status_update tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: update_project, create_project_status_update, missing_tool, missing_data diff --git a/.github/workflows/tidy.lock.yml b/.github/workflows/tidy.lock.yml index 7508a4417e..dd74335017 100644 --- a/.github/workflows/tidy.lock.yml +++ b/.github/workflows/tidy.lock.yml @@ -142,29 +142,11 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Pull Request** + Tools: create_pull_request, push_to_pull_request_branch, missing_tool, missing_data - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. - **Pushing Changes to a Pull Request Branch** - - To push changes to the branch of a pull request: - 1. Make any file changes directly in the working directory. - 2. Add and commit your changes to the local copy of the pull request branch. Be careful to add exactly the files you intend, and verify you haven't deleted or changed any files you didn't intend to. - 3. Push the branch to the repo by using the push_to_pull_request_branch tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + push_to_pull_request_branch: commit changes locally (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/typist.lock.yml b/.github/workflows/typist.lock.yml index 623ab2d211..8d5b5bcc51 100644 --- a/.github/workflows/typist.lock.yml +++ b/.github/workflows/typist.lock.yml @@ -111,17 +111,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_discussion, missing_tool, missing_data diff --git a/.github/workflows/ubuntu-image-analyzer.lock.yml b/.github/workflows/ubuntu-image-analyzer.lock.yml index 36365981d3..e1dc9da12b 100644 --- a/.github/workflows/ubuntu-image-analyzer.lock.yml +++ b/.github/workflows/ubuntu-image-analyzer.lock.yml @@ -111,22 +111,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Pull Request** + Tools: create_pull_request, missing_tool, missing_data - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/unbloat-docs.lock.yml b/.github/workflows/unbloat-docs.lock.yml index 01c43c630a..db7ea9ac03 100644 --- a/.github/workflows/unbloat-docs.lock.yml +++ b/.github/workflows/unbloat-docs.lock.yml @@ -139,34 +139,11 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** + Tools: add_comment, create_pull_request, upload_asset, missing_tool, missing_data - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Uploading Assets** - - To upload files as URL-addressable assets: - 1. Use the upload_asset tool from safeoutputs. - 2. Provide the path to the file you want to upload. - 3. The tool will copy the file to a staging area and return a GitHub raw content URL. - 4. Assets are uploaded to an orphaned git branch after workflow completion. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). diff --git a/.github/workflows/video-analyzer.lock.yml b/.github/workflows/video-analyzer.lock.yml index 8824018128..bb4583e068 100644 --- a/.github/workflows/video-analyzer.lock.yml +++ b/.github/workflows/video-analyzer.lock.yml @@ -115,17 +115,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, missing_tool, missing_data diff --git a/.github/workflows/weekly-editors-health-check.lock.yml b/.github/workflows/weekly-editors-health-check.lock.yml index eac8c68939..c5cbdc4dd1 100644 --- a/.github/workflows/weekly-editors-health-check.lock.yml +++ b/.github/workflows/weekly-editors-health-check.lock.yml @@ -109,30 +109,11 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Pull Request** + Tools: create_pull_request, upload_asset, missing_tool, missing_data - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. - **Uploading Assets** - - To upload files as URL-addressable assets: - 1. Use the upload_asset tool from safeoutputs. - 2. Provide the path to the file you want to upload. - 3. The tool will copy the file to a staging area and return a GitHub raw content URL. - 4. Assets are uploaded to an orphaned git branch after workflow completion. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). diff --git a/.github/workflows/weekly-issue-summary.lock.yml b/.github/workflows/weekly-issue-summary.lock.yml index 194022468b..f312f5e647 100644 --- a/.github/workflows/weekly-issue-summary.lock.yml +++ b/.github/workflows/weekly-issue-summary.lock.yml @@ -106,25 +106,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Discussion** + Tools: create_discussion, upload_asset, missing_tool, missing_data - To create a discussion, use the create_discussion tool from safeoutputs. - - **Uploading Assets** - - To upload files as URL-addressable assets: - 1. Use the upload_asset tool from safeoutputs. - 2. Provide the path to the file you want to upload. - 3. The tool will copy the file to a staging area and return a GitHub raw content URL. - 4. Assets are uploaded to an orphaned git branch after workflow completion. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). diff --git a/.github/workflows/weekly-safe-outputs-spec-review.lock.yml b/.github/workflows/weekly-safe-outputs-spec-review.lock.yml index d28f960226..2665b5638c 100644 --- a/.github/workflows/weekly-safe-outputs-spec-review.lock.yml +++ b/.github/workflows/weekly-safe-outputs-spec-review.lock.yml @@ -108,22 +108,9 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating a Pull Request** + Tools: create_pull_request, missing_tool, missing_data - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. diff --git a/.github/workflows/workflow-generator.lock.yml b/.github/workflows/workflow-generator.lock.yml index a1c6ec0bde..b87bdb1dbf 100644 --- a/.github/workflows/workflow-generator.lock.yml +++ b/.github/workflows/workflow-generator.lock.yml @@ -136,21 +136,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Updating an Issue** - - To update an issue, use the update_issue tool from safeoutputs. - - **Assigning to an Agent** - - To assign an issue or pull request to a GitHub Copilot agent, use the assign_to_agent tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: update_issue, assign_to_agent, missing_tool, missing_data diff --git a/.github/workflows/workflow-health-manager.lock.yml b/.github/workflows/workflow-health-manager.lock.yml index 9557341a75..5fea1cdabc 100644 --- a/.github/workflows/workflow-health-manager.lock.yml +++ b/.github/workflows/workflow-health-manager.lock.yml @@ -115,25 +115,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Adding a Comment to an Issue or Pull Request** - - To add a comment to an issue or pull request, use the add_comment tool from safeoutputs. - - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Updating an Issue** - - To update an issue, use the update_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: add_comment, create_issue, update_issue, missing_tool, missing_data diff --git a/.github/workflows/workflow-normalizer.lock.yml b/.github/workflows/workflow-normalizer.lock.yml index 32783ce4af..06c1329aed 100644 --- a/.github/workflows/workflow-normalizer.lock.yml +++ b/.github/workflows/workflow-normalizer.lock.yml @@ -112,17 +112,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, missing_tool, missing_data diff --git a/.github/workflows/workflow-skill-extractor.lock.yml b/.github/workflows/workflow-skill-extractor.lock.yml index 0d5f844120..2b7aa3593d 100644 --- a/.github/workflows/workflow-skill-extractor.lock.yml +++ b/.github/workflows/workflow-skill-extractor.lock.yml @@ -112,21 +112,7 @@ jobs: cat "/opt/gh-aw/prompts/safe_outputs_prompt.md" cat << 'GH_AW_PROMPT_EOF' - **Creating an Issue** - - To create an issue, use the create_issue tool from safeoutputs. - - **Creating a Discussion** - - To create a discussion, use the create_discussion tool from safeoutputs. - - **Reporting Missing Tools or Functionality** - - To report a missing tool or capability, use the missing_tool tool from safeoutputs. - - **Reporting Missing Data** - - To report missing data required to achieve a goal, use the missing_data tool from safeoutputs. + Tools: create_issue, create_discussion, missing_tool, missing_data diff --git a/actions/setup/md/safe_outputs_prompt.md b/actions/setup/md/safe_outputs_prompt.md index a389cd45b9..fccb9e9d20 100644 --- a/actions/setup/md/safe_outputs_prompt.md +++ b/actions/setup/md/safe_outputs_prompt.md @@ -1,26 +1,6 @@ -GitHub API Access Instructions - -The gh CLI is NOT authenticated. Do NOT use gh commands for GitHub operations. - -To create or modify GitHub resources (issues, discussions, pull requests, etc.), you MUST call the appropriate safe output tool from the safeoutputs MCP server. Simply writing content will NOT work - the workflow requires actual tool calls. - -Temporary IDs: Some safe output tools support a temporary ID field (usually named temporary_id) so you can reference newly-created items elsewhere in the SAME agent output (for example, using #aw_abc1 in a later body). - -**IMPORTANT - temporary_id format rules:** -- If you DON'T need to reference the item later, OMIT the temporary_id field entirely (it will be auto-generated if needed) -- If you DO need cross-references/chaining, you MUST match this EXACT validation regex: /^aw_[A-Za-z0-9]{3,8}$/i -- Format: aw_ prefix followed by 3 to 8 alphanumeric characters (A-Z, a-z, 0-9, case-insensitive) -- Valid alphanumeric characters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 -- INVALID examples: aw_ab (too short), aw_123456789 (too long), aw_test-id (contains hyphen), aw_id_123 (contains underscore) -- VALID examples: aw_abc, aw_abc1, aw_Test123, aw_A1B2C3D4, aw_12345678 -- To generate valid IDs: use 3-8 random alphanumeric characters or omit the field to let the system auto-generate - -Do NOT invent other aw_* formats — downstream steps will reject them with validation errors matching against /^aw_[A-Za-z0-9]{3,8}$/i. - -**Critical**: Tool calls write structured data that downstream jobs process. Without tool calls, follow-up actions will be skipped. - -**Note**: If you made no other safe output tool calls during this workflow execution, call the "noop" tool to provide a status message indicating completion or that no actions were needed. +gh CLI is NOT authenticated. Use safeoutputs MCP server tools for all GitHub operations — tool calls required. If no tool was called, use noop. +temporary_id: optional cross-reference field (e.g. use #aw_abc1 in a body). Format: aw_ + 3–8 alphanumeric chars (/^aw_[A-Za-z0-9]{3,8}$/). Omit when not needed. diff --git a/pkg/workflow/prompts_test.go b/pkg/workflow/prompts_test.go index 4d7647096a..4ac1d6dd68 100644 --- a/pkg/workflow/prompts_test.go +++ b/pkg/workflow/prompts_test.go @@ -44,9 +44,6 @@ func TestGenerateSafeOutputsPromptStep_IncludesWhenEnabled(t *testing.T) { if !strings.Contains(output, "create_issue") { t.Error("Expected prompt to include create_issue tool name") } - if !strings.Contains(output, "Creating an Issue") { - t.Error("Expected prompt to include 'Creating an Issue' heading") - } } func TestGenerateSafeOutputsPromptStep_SkippedWhenDisabled(t *testing.T) { @@ -106,25 +103,11 @@ func TestSafeOutputsPrompt_IncludesPerToolInstructions(t *testing.T) { t.Fatal("Expected section in generated prompt") } - // Verify per-tool instructions are present for each enabled tool - toolTests := []struct { - toolName string - heading string - description string - }{ - {"create_issue", "Creating an Issue", "To create an issue, use the create_issue tool"}, - {"add_comment", "Adding a Comment", "To add a comment to an issue or pull request, use the add_comment tool"}, - {"create_discussion", "Creating a Discussion", "To create a discussion, use the create_discussion tool"}, - {"update_issue", "Updating an Issue", "To update an issue, use the update_issue tool"}, - } - - for _, tt := range toolTests { - t.Run(tt.toolName, func(t *testing.T) { - if !strings.Contains(output, tt.toolName) { - t.Errorf("Expected per-tool instruction to include tool name %q", tt.toolName) - } - if !strings.Contains(output, tt.heading) { - t.Errorf("Expected per-tool instruction heading %q", tt.heading) + // Verify enabled tool names are present + for _, toolName := range []string{"create_issue", "add_comment", "create_discussion", "update_issue"} { + t.Run(toolName, func(t *testing.T) { + if !strings.Contains(output, toolName) { + t.Errorf("Expected per-tool instruction to include tool name %q", toolName) } }) } diff --git a/pkg/workflow/unified_prompt_step.go b/pkg/workflow/unified_prompt_step.go index d6e08d7095..f6510a1fa3 100644 --- a/pkg/workflow/unified_prompt_step.go +++ b/pkg/workflow/unified_prompt_step.go @@ -600,199 +600,139 @@ func generateSafeOutputsPerToolInstructions(b *strings.Builder, safeOutputs *Saf safeOutputsPromptLog.Print("Generating safe outputs per-tool instructions") + // Build compact list of enabled tool names + var tools []string if safeOutputs.AddComments != nil { - b.WriteString("**Adding a Comment to an Issue or Pull Request**\n\n") - fmt.Fprintf(b, "To add a comment to an issue or pull request, use the add_comment tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "add_comment") } - if safeOutputs.CreateIssues != nil { - b.WriteString("**Creating an Issue**\n\n") - fmt.Fprintf(b, "To create an issue, use the create_issue tool from %s.\n\n", constants.SafeOutputsMCPServerID) - if safeOutputs.AutoInjectedCreateIssue { - b.WriteString("**IMPORTANT**: Report your findings or results by creating a GitHub issue using the create_issue tool. If you have no meaningful results to report, call the noop tool instead.\n\n") - } + tools = append(tools, "create_issue") } - if safeOutputs.CloseIssues != nil { - b.WriteString("**Closing an Issue**\n\n") - fmt.Fprintf(b, "To close an issue, use the close_issue tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "close_issue") } - if safeOutputs.UpdateIssues != nil { - b.WriteString("**Updating an Issue**\n\n") - fmt.Fprintf(b, "To update an issue, use the update_issue tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "update_issue") } - if safeOutputs.CreateDiscussions != nil { - b.WriteString("**Creating a Discussion**\n\n") - fmt.Fprintf(b, "To create a discussion, use the create_discussion tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "create_discussion") } - if safeOutputs.UpdateDiscussions != nil { - b.WriteString("**Updating a Discussion**\n\n") - fmt.Fprintf(b, "To update a discussion, use the update_discussion tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "update_discussion") } - if safeOutputs.CloseDiscussions != nil { - b.WriteString("**Closing a Discussion**\n\n") - fmt.Fprintf(b, "To close a discussion, use the close_discussion tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "close_discussion") } - if safeOutputs.CreateAgentSessions != nil { - b.WriteString("**Creating an Agent Session**\n\n") - fmt.Fprintf(b, "To create a GitHub Copilot agent session, use the create_agent_session tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "create_agent_session") } - if safeOutputs.CreatePullRequests != nil { - b.WriteString("**Creating a Pull Request**\n\n") - b.WriteString("To create a pull request:\n") - b.WriteString("1. Make any file changes directly in the working directory.\n") - b.WriteString("2. If you haven't done so already, create a local branch using an appropriate unique name.\n") - b.WriteString("3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to.\n") - b.WriteString("4. Do not push your changes. That will be done by the tool.\n") - fmt.Fprintf(b, "5. Create the pull request with the create_pull_request tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "create_pull_request") } - if safeOutputs.ClosePullRequests != nil { - b.WriteString("**Closing a Pull Request**\n\n") - fmt.Fprintf(b, "To close a pull request, use the close_pull_request tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "close_pull_request") } - if safeOutputs.UpdatePullRequests != nil { - b.WriteString("**Updating a Pull Request**\n\n") - fmt.Fprintf(b, "To update a pull request title or body, use the update_pull_request tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "update_pull_request") } - if safeOutputs.MarkPullRequestAsReadyForReview != nil { - b.WriteString("**Marking a Pull Request as Ready for Review**\n\n") - fmt.Fprintf(b, "To mark a pull request as ready for review, use the mark_pull_request_as_ready_for_review tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "mark_pull_request_as_ready_for_review") } - if safeOutputs.CreatePullRequestReviewComments != nil { - b.WriteString("**Creating a Pull Request Review Comment**\n\n") - fmt.Fprintf(b, "To create a pull request review comment, use the create_pull_request_review_comment tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "create_pull_request_review_comment") } - if safeOutputs.SubmitPullRequestReview != nil { - b.WriteString("**Submitting a Pull Request Review**\n\n") - fmt.Fprintf(b, "To submit a pull request review (APPROVE, REQUEST_CHANGES, or COMMENT), use the submit_pull_request_review tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "submit_pull_request_review") } - if safeOutputs.ReplyToPullRequestReviewComment != nil { - b.WriteString("**Replying to a Pull Request Review Comment**\n\n") - fmt.Fprintf(b, "To reply to an existing review comment on a pull request, use the reply_to_pull_request_review_comment tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "reply_to_pull_request_review_comment") } - if safeOutputs.ResolvePullRequestReviewThread != nil { - b.WriteString("**Resolving a Pull Request Review Thread**\n\n") - fmt.Fprintf(b, "To resolve a review thread on a pull request, use the resolve_pull_request_review_thread tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "resolve_pull_request_review_thread") } - if safeOutputs.AddLabels != nil { - b.WriteString("**Adding Labels to Issues or Pull Requests**\n\n") - fmt.Fprintf(b, "To add labels to an issue or pull request, use the add_labels tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "add_labels") } - if safeOutputs.RemoveLabels != nil { - b.WriteString("**Removing Labels from Issues or Pull Requests**\n\n") - fmt.Fprintf(b, "To remove labels from an issue or pull request, use the remove_labels tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "remove_labels") } - if safeOutputs.AddReviewer != nil { - b.WriteString("**Adding a Reviewer to a Pull Request**\n\n") - fmt.Fprintf(b, "To add a reviewer to a pull request, use the add_reviewer tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "add_reviewer") } - if safeOutputs.AssignMilestone != nil { - b.WriteString("**Assigning a Milestone**\n\n") - fmt.Fprintf(b, "To assign a milestone to an issue or pull request, use the assign_milestone tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "assign_milestone") } - if safeOutputs.AssignToAgent != nil { - b.WriteString("**Assigning to an Agent**\n\n") - fmt.Fprintf(b, "To assign an issue or pull request to a GitHub Copilot agent, use the assign_to_agent tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "assign_to_agent") } - if safeOutputs.AssignToUser != nil { - b.WriteString("**Assigning to a User**\n\n") - fmt.Fprintf(b, "To assign an issue or pull request to a user, use the assign_to_user tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "assign_to_user") } - if safeOutputs.UnassignFromUser != nil { - b.WriteString("**Unassigning from a User**\n\n") - fmt.Fprintf(b, "To remove a user assignee from an issue or pull request, use the unassign_from_user tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "unassign_from_user") } - if safeOutputs.PushToPullRequestBranch != nil { - b.WriteString("**Pushing Changes to a Pull Request Branch**\n\n") - b.WriteString("To push changes to the branch of a pull request:\n") - b.WriteString("1. Make any file changes directly in the working directory.\n") - b.WriteString("2. Add and commit your changes to the local copy of the pull request branch. Be careful to add exactly the files you intend, and verify you haven't deleted or changed any files you didn't intend to.\n") - fmt.Fprintf(b, "3. Push the branch to the repo by using the push_to_pull_request_branch tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "push_to_pull_request_branch") } - if safeOutputs.CreateCodeScanningAlerts != nil { - b.WriteString("**Creating a Code Scanning Alert**\n\n") - fmt.Fprintf(b, "To create a code scanning alert, use the create_code_scanning_alert tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "create_code_scanning_alert") } - if safeOutputs.AutofixCodeScanningAlert != nil { - b.WriteString("**Autofixing a Code Scanning Alert**\n\n") - fmt.Fprintf(b, "To autofix a code scanning alert, use the autofix_code_scanning_alert tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "autofix_code_scanning_alert") } - if safeOutputs.UploadAssets != nil { - b.WriteString("**Uploading Assets**\n\n") - b.WriteString("To upload files as URL-addressable assets:\n") - fmt.Fprintf(b, "1. Use the upload_asset tool from %s.\n", constants.SafeOutputsMCPServerID) - b.WriteString("2. Provide the path to the file you want to upload.\n") - b.WriteString("3. The tool will copy the file to a staging area and return a GitHub raw content URL.\n") - b.WriteString("4. Assets are uploaded to an orphaned git branch after workflow completion.\n\n") + tools = append(tools, "upload_asset") } - if safeOutputs.UpdateRelease != nil { - b.WriteString("**Updating a Release**\n\n") - fmt.Fprintf(b, "To update a GitHub release description, use the update_release tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "update_release") } - if safeOutputs.UpdateProjects != nil { - b.WriteString("**Updating a Project**\n\n") - fmt.Fprintf(b, "To create, add items to, or update a project board, use the update_project tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "update_project") } - if safeOutputs.CreateProjects != nil { - b.WriteString("**Creating a Project**\n\n") - fmt.Fprintf(b, "To create a GitHub Projects V2 project, use the create_project tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "create_project") } - if safeOutputs.CreateProjectStatusUpdates != nil { - b.WriteString("**Creating a Project Status Update**\n\n") - fmt.Fprintf(b, "To create a project status update, use the create_project_status_update tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "create_project_status_update") } - if safeOutputs.LinkSubIssue != nil { - b.WriteString("**Linking a Sub-Issue**\n\n") - fmt.Fprintf(b, "To link an issue as a sub-issue of another issue, use the link_sub_issue tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "link_sub_issue") } - if safeOutputs.HideComment != nil { - b.WriteString("**Hiding a Comment**\n\n") - fmt.Fprintf(b, "To hide a comment, use the hide_comment tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "hide_comment") } - if safeOutputs.DispatchWorkflow != nil { - b.WriteString("**Dispatching a Workflow**\n\n") - fmt.Fprintf(b, "To dispatch a workflow_dispatch event to another workflow, use the dispatch_workflow tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "dispatch_workflow") } - if safeOutputs.MissingTool != nil { - b.WriteString("**Reporting Missing Tools or Functionality**\n\n") - fmt.Fprintf(b, "To report a missing tool or capability, use the missing_tool tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "missing_tool") } - if safeOutputs.MissingData != nil { - b.WriteString("**Reporting Missing Data**\n\n") - fmt.Fprintf(b, "To report missing data required to achieve a goal, use the missing_data tool from %s.\n\n", constants.SafeOutputsMCPServerID) + tools = append(tools, "missing_data") + } + + if len(tools) == 0 { + return + } + + fmt.Fprintf(b, "Tools: %s\n\n", strings.Join(tools, ", ")) + + // Special multi-step instructions for complex tools + if safeOutputs.CreatePullRequests != nil { + fmt.Fprintf(b, "create_pull_request: commit changes to a local branch (do not push), then call this tool from %s.\n\n", constants.SafeOutputsMCPServerID) + } + + if safeOutputs.PushToPullRequestBranch != nil { + fmt.Fprintf(b, "push_to_pull_request_branch: commit changes locally (do not push), then call this tool from %s.\n\n", constants.SafeOutputsMCPServerID) + } + + if safeOutputs.UploadAssets != nil { + fmt.Fprintf(b, "upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (%s).\n\n", constants.SafeOutputsMCPServerID) + } + + // Auto-injected create_issue special notice + if safeOutputs.CreateIssues != nil && safeOutputs.AutoInjectedCreateIssue { + b.WriteString("**IMPORTANT**: Report your findings or results by creating a GitHub issue using the create_issue tool. If you have no meaningful results to report, call the noop tool instead.\n\n") } } From 0f53e73b419bd0cc9abb55c0a1c72abbec89b010 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sun, 22 Feb 2026 20:04:29 +0000 Subject: [PATCH 4/7] Restore full step-by-step instructions for create_pull_request and push_to_pull_request_branch Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- .github/workflows/changeset.lock.yml | 7 ++++++- .github/workflows/ci-coach.lock.yml | 9 ++++++++- .github/workflows/cloclo.lock.yml | 9 ++++++++- .github/workflows/code-scanning-fixer.lock.yml | 9 ++++++++- .github/workflows/code-simplifier.lock.yml | 9 ++++++++- .github/workflows/craft.lock.yml | 7 ++++++- .github/workflows/daily-doc-updater.lock.yml | 9 ++++++++- .../daily-rendering-scripts-verifier.lock.yml | 9 ++++++++- .../workflows/daily-workflow-updater.lock.yml | 9 ++++++++- .../developer-docs-consolidator.lock.yml | 9 ++++++++- .github/workflows/dictation-prompt.lock.yml | 9 ++++++++- .github/workflows/functional-pragmatist.lock.yml | 9 ++++++++- .../workflows/github-mcp-tools-report.lock.yml | 9 ++++++++- .github/workflows/glossary-maintainer.lock.yml | 9 ++++++++- .github/workflows/go-logger.lock.yml | 9 ++++++++- .github/workflows/hourly-ci-cleaner.lock.yml | 9 ++++++++- .github/workflows/instructions-janitor.lock.yml | 9 ++++++++- .github/workflows/jsweep.lock.yml | 9 ++++++++- .../workflows/layout-spec-maintainer.lock.yml | 9 ++++++++- .github/workflows/mergefest.lock.yml | 7 ++++++- .github/workflows/poem-bot.lock.yml | 16 ++++++++++++++-- .github/workflows/q.lock.yml | 9 ++++++++- .github/workflows/refiner.lock.yml | 9 ++++++++- .github/workflows/slide-deck-maintainer.lock.yml | 9 ++++++++- .github/workflows/smoke-claude.lock.yml | 7 ++++++- .github/workflows/smoke-multi-pr.lock.yml | 9 ++++++++- .github/workflows/smoke-project.lock.yml | 9 ++++++++- .github/workflows/technical-doc-writer.lock.yml | 9 ++++++++- .../test-create-pr-error-handling.lock.yml | 9 ++++++++- .github/workflows/tidy.lock.yml | 16 ++++++++++++++-- .github/workflows/ubuntu-image-analyzer.lock.yml | 9 ++++++++- .github/workflows/unbloat-docs.lock.yml | 9 ++++++++- .../weekly-editors-health-check.lock.yml | 9 ++++++++- .../weekly-safe-outputs-spec-review.lock.yml | 9 ++++++++- pkg/workflow/unified_prompt_step.go | 14 ++++++++++++-- 35 files changed, 288 insertions(+), 38 deletions(-) diff --git a/.github/workflows/changeset.lock.yml b/.github/workflows/changeset.lock.yml index 57dac40f58..ec5bb6303d 100644 --- a/.github/workflows/changeset.lock.yml +++ b/.github/workflows/changeset.lock.yml @@ -143,7 +143,12 @@ jobs: Tools: update_pull_request, push_to_pull_request_branch, missing_tool, missing_data - push_to_pull_request_branch: commit changes locally (do not push), then call this tool from safeoutputs. + **Pushing Changes to a Pull Request Branch** + + To push changes to the branch of a pull request: + 1. Make any file changes directly in the working directory. + 2. Add and commit your changes to the local copy of the pull request branch. Be careful to add exactly the files you intend, and verify you haven't deleted or changed any files you didn't intend to. + 3. Push the branch to the repo by using the push_to_pull_request_branch tool from safeoutputs. diff --git a/.github/workflows/ci-coach.lock.yml b/.github/workflows/ci-coach.lock.yml index 3f2a79e6eb..dbe52df018 100644 --- a/.github/workflows/ci-coach.lock.yml +++ b/.github/workflows/ci-coach.lock.yml @@ -118,7 +118,14 @@ jobs: Tools: create_pull_request, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** + + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. diff --git a/.github/workflows/cloclo.lock.yml b/.github/workflows/cloclo.lock.yml index 893f2ec560..e664a98367 100644 --- a/.github/workflows/cloclo.lock.yml +++ b/.github/workflows/cloclo.lock.yml @@ -178,7 +178,14 @@ jobs: Tools: add_comment, create_pull_request, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** + + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. diff --git a/.github/workflows/code-scanning-fixer.lock.yml b/.github/workflows/code-scanning-fixer.lock.yml index 99482bf0bf..8834163b32 100644 --- a/.github/workflows/code-scanning-fixer.lock.yml +++ b/.github/workflows/code-scanning-fixer.lock.yml @@ -112,7 +112,14 @@ jobs: Tools: create_pull_request, add_labels, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** + + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. diff --git a/.github/workflows/code-simplifier.lock.yml b/.github/workflows/code-simplifier.lock.yml index 1faf3fce00..2b4470ee2f 100644 --- a/.github/workflows/code-simplifier.lock.yml +++ b/.github/workflows/code-simplifier.lock.yml @@ -117,7 +117,14 @@ jobs: Tools: create_pull_request, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** + + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. diff --git a/.github/workflows/craft.lock.yml b/.github/workflows/craft.lock.yml index a3ec6691c5..bc5db41bdc 100644 --- a/.github/workflows/craft.lock.yml +++ b/.github/workflows/craft.lock.yml @@ -133,7 +133,12 @@ jobs: Tools: add_comment, push_to_pull_request_branch, missing_tool, missing_data - push_to_pull_request_branch: commit changes locally (do not push), then call this tool from safeoutputs. + **Pushing Changes to a Pull Request Branch** + + To push changes to the branch of a pull request: + 1. Make any file changes directly in the working directory. + 2. Add and commit your changes to the local copy of the pull request branch. Be careful to add exactly the files you intend, and verify you haven't deleted or changed any files you didn't intend to. + 3. Push the branch to the repo by using the push_to_pull_request_branch tool from safeoutputs. diff --git a/.github/workflows/daily-doc-updater.lock.yml b/.github/workflows/daily-doc-updater.lock.yml index 0458434861..8ad52c24a9 100644 --- a/.github/workflows/daily-doc-updater.lock.yml +++ b/.github/workflows/daily-doc-updater.lock.yml @@ -111,7 +111,14 @@ jobs: Tools: create_pull_request, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** + + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. diff --git a/.github/workflows/daily-rendering-scripts-verifier.lock.yml b/.github/workflows/daily-rendering-scripts-verifier.lock.yml index 1353c66d5c..7829e2fb70 100644 --- a/.github/workflows/daily-rendering-scripts-verifier.lock.yml +++ b/.github/workflows/daily-rendering-scripts-verifier.lock.yml @@ -118,7 +118,14 @@ jobs: Tools: create_pull_request, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** + + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. diff --git a/.github/workflows/daily-workflow-updater.lock.yml b/.github/workflows/daily-workflow-updater.lock.yml index bfb80430da..37deec6ab3 100644 --- a/.github/workflows/daily-workflow-updater.lock.yml +++ b/.github/workflows/daily-workflow-updater.lock.yml @@ -110,7 +110,14 @@ jobs: Tools: create_pull_request, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** + + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. diff --git a/.github/workflows/developer-docs-consolidator.lock.yml b/.github/workflows/developer-docs-consolidator.lock.yml index adceb3b374..72aa0cf736 100644 --- a/.github/workflows/developer-docs-consolidator.lock.yml +++ b/.github/workflows/developer-docs-consolidator.lock.yml @@ -115,7 +115,14 @@ jobs: Tools: create_discussion, create_pull_request, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** + + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. diff --git a/.github/workflows/dictation-prompt.lock.yml b/.github/workflows/dictation-prompt.lock.yml index 7f734bacff..c01cad62d6 100644 --- a/.github/workflows/dictation-prompt.lock.yml +++ b/.github/workflows/dictation-prompt.lock.yml @@ -113,7 +113,14 @@ jobs: Tools: create_pull_request, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** + + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. diff --git a/.github/workflows/functional-pragmatist.lock.yml b/.github/workflows/functional-pragmatist.lock.yml index ae83545c13..9885663e71 100644 --- a/.github/workflows/functional-pragmatist.lock.yml +++ b/.github/workflows/functional-pragmatist.lock.yml @@ -113,7 +113,14 @@ jobs: Tools: create_pull_request, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** + + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. diff --git a/.github/workflows/github-mcp-tools-report.lock.yml b/.github/workflows/github-mcp-tools-report.lock.yml index 0f1256b971..4aa0a62cd4 100644 --- a/.github/workflows/github-mcp-tools-report.lock.yml +++ b/.github/workflows/github-mcp-tools-report.lock.yml @@ -115,7 +115,14 @@ jobs: Tools: create_discussion, create_pull_request, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** + + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. diff --git a/.github/workflows/glossary-maintainer.lock.yml b/.github/workflows/glossary-maintainer.lock.yml index b0977106d6..fa9e864ab1 100644 --- a/.github/workflows/glossary-maintainer.lock.yml +++ b/.github/workflows/glossary-maintainer.lock.yml @@ -115,7 +115,14 @@ jobs: Tools: create_pull_request, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** + + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. diff --git a/.github/workflows/go-logger.lock.yml b/.github/workflows/go-logger.lock.yml index 7168088577..adba9b7355 100644 --- a/.github/workflows/go-logger.lock.yml +++ b/.github/workflows/go-logger.lock.yml @@ -115,7 +115,14 @@ jobs: Tools: create_pull_request, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** + + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. diff --git a/.github/workflows/hourly-ci-cleaner.lock.yml b/.github/workflows/hourly-ci-cleaner.lock.yml index 640fcddbd1..b2abcca2f8 100644 --- a/.github/workflows/hourly-ci-cleaner.lock.yml +++ b/.github/workflows/hourly-ci-cleaner.lock.yml @@ -118,7 +118,14 @@ jobs: Tools: create_pull_request, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** + + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. diff --git a/.github/workflows/instructions-janitor.lock.yml b/.github/workflows/instructions-janitor.lock.yml index 5d21371446..d4d152eb9e 100644 --- a/.github/workflows/instructions-janitor.lock.yml +++ b/.github/workflows/instructions-janitor.lock.yml @@ -111,7 +111,14 @@ jobs: Tools: create_pull_request, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** + + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. diff --git a/.github/workflows/jsweep.lock.yml b/.github/workflows/jsweep.lock.yml index b830c94518..8e3f100a72 100644 --- a/.github/workflows/jsweep.lock.yml +++ b/.github/workflows/jsweep.lock.yml @@ -111,7 +111,14 @@ jobs: Tools: create_pull_request, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** + + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. diff --git a/.github/workflows/layout-spec-maintainer.lock.yml b/.github/workflows/layout-spec-maintainer.lock.yml index 1e48863841..bff19ccc0b 100644 --- a/.github/workflows/layout-spec-maintainer.lock.yml +++ b/.github/workflows/layout-spec-maintainer.lock.yml @@ -111,7 +111,14 @@ jobs: Tools: create_pull_request, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** + + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. diff --git a/.github/workflows/mergefest.lock.yml b/.github/workflows/mergefest.lock.yml index 64dfcb7304..16abb448cb 100644 --- a/.github/workflows/mergefest.lock.yml +++ b/.github/workflows/mergefest.lock.yml @@ -131,7 +131,12 @@ jobs: Tools: push_to_pull_request_branch, missing_tool, missing_data - push_to_pull_request_branch: commit changes locally (do not push), then call this tool from safeoutputs. + **Pushing Changes to a Pull Request Branch** + + To push changes to the branch of a pull request: + 1. Make any file changes directly in the working directory. + 2. Add and commit your changes to the local copy of the pull request branch. Be careful to add exactly the files you intend, and verify you haven't deleted or changed any files you didn't intend to. + 3. Push the branch to the repo by using the push_to_pull_request_branch tool from safeoutputs. diff --git a/.github/workflows/poem-bot.lock.yml b/.github/workflows/poem-bot.lock.yml index 23dba46e28..32b16a7858 100644 --- a/.github/workflows/poem-bot.lock.yml +++ b/.github/workflows/poem-bot.lock.yml @@ -149,9 +149,21 @@ jobs: Tools: add_comment, create_issue, update_issue, create_discussion, create_agent_session, create_pull_request, close_pull_request, create_pull_request_review_comment, add_labels, push_to_pull_request_branch, upload_asset, link_sub_issue, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** - push_to_pull_request_branch: commit changes locally (do not push), then call this tool from safeoutputs. + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. + + **Pushing Changes to a Pull Request Branch** + + To push changes to the branch of a pull request: + 1. Make any file changes directly in the working directory. + 2. Add and commit your changes to the local copy of the pull request branch. Be careful to add exactly the files you intend, and verify you haven't deleted or changed any files you didn't intend to. + 3. Push the branch to the repo by using the push_to_pull_request_branch tool from safeoutputs. upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). diff --git a/.github/workflows/q.lock.yml b/.github/workflows/q.lock.yml index 397959c135..9dd7c1e74d 100644 --- a/.github/workflows/q.lock.yml +++ b/.github/workflows/q.lock.yml @@ -171,7 +171,14 @@ jobs: Tools: add_comment, create_pull_request, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** + + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. diff --git a/.github/workflows/refiner.lock.yml b/.github/workflows/refiner.lock.yml index ba86c3996c..4e57b3f6dc 100644 --- a/.github/workflows/refiner.lock.yml +++ b/.github/workflows/refiner.lock.yml @@ -135,7 +135,14 @@ jobs: Tools: add_comment, create_pull_request, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** + + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. diff --git a/.github/workflows/slide-deck-maintainer.lock.yml b/.github/workflows/slide-deck-maintainer.lock.yml index 21052311c6..116ebea9d7 100644 --- a/.github/workflows/slide-deck-maintainer.lock.yml +++ b/.github/workflows/slide-deck-maintainer.lock.yml @@ -121,7 +121,14 @@ jobs: Tools: create_pull_request, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** + + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. diff --git a/.github/workflows/smoke-claude.lock.yml b/.github/workflows/smoke-claude.lock.yml index 6b3beadb09..789a17a82c 100644 --- a/.github/workflows/smoke-claude.lock.yml +++ b/.github/workflows/smoke-claude.lock.yml @@ -163,7 +163,12 @@ jobs: Tools: add_comment, create_issue, close_pull_request, update_pull_request, create_pull_request_review_comment, submit_pull_request_review, resolve_pull_request_review_thread, add_labels, add_reviewer, push_to_pull_request_branch, missing_tool, missing_data - push_to_pull_request_branch: commit changes locally (do not push), then call this tool from safeoutputs. + **Pushing Changes to a Pull Request Branch** + + To push changes to the branch of a pull request: + 1. Make any file changes directly in the working directory. + 2. Add and commit your changes to the local copy of the pull request branch. Be careful to add exactly the files you intend, and verify you haven't deleted or changed any files you didn't intend to. + 3. Push the branch to the repo by using the push_to_pull_request_branch tool from safeoutputs. diff --git a/.github/workflows/smoke-multi-pr.lock.yml b/.github/workflows/smoke-multi-pr.lock.yml index 32478aabb2..8ad6fc6b3e 100644 --- a/.github/workflows/smoke-multi-pr.lock.yml +++ b/.github/workflows/smoke-multi-pr.lock.yml @@ -148,7 +148,14 @@ jobs: Tools: add_comment, create_pull_request, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** + + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. diff --git a/.github/workflows/smoke-project.lock.yml b/.github/workflows/smoke-project.lock.yml index f0599d495c..0cfc643543 100644 --- a/.github/workflows/smoke-project.lock.yml +++ b/.github/workflows/smoke-project.lock.yml @@ -146,7 +146,14 @@ jobs: Tools: add_comment, create_issue, create_pull_request, add_labels, remove_labels, update_project, create_project_status_update, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** + + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. diff --git a/.github/workflows/technical-doc-writer.lock.yml b/.github/workflows/technical-doc-writer.lock.yml index 5654cfdf3a..ac6dfb8c10 100644 --- a/.github/workflows/technical-doc-writer.lock.yml +++ b/.github/workflows/technical-doc-writer.lock.yml @@ -119,7 +119,14 @@ jobs: Tools: add_comment, create_pull_request, upload_asset, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** + + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). diff --git a/.github/workflows/test-create-pr-error-handling.lock.yml b/.github/workflows/test-create-pr-error-handling.lock.yml index fc91c4dc26..f554ec0db5 100644 --- a/.github/workflows/test-create-pr-error-handling.lock.yml +++ b/.github/workflows/test-create-pr-error-handling.lock.yml @@ -108,7 +108,14 @@ jobs: Tools: create_pull_request, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** + + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. diff --git a/.github/workflows/tidy.lock.yml b/.github/workflows/tidy.lock.yml index dd74335017..22f765adac 100644 --- a/.github/workflows/tidy.lock.yml +++ b/.github/workflows/tidy.lock.yml @@ -144,9 +144,21 @@ jobs: Tools: create_pull_request, push_to_pull_request_branch, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** - push_to_pull_request_branch: commit changes locally (do not push), then call this tool from safeoutputs. + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. + + **Pushing Changes to a Pull Request Branch** + + To push changes to the branch of a pull request: + 1. Make any file changes directly in the working directory. + 2. Add and commit your changes to the local copy of the pull request branch. Be careful to add exactly the files you intend, and verify you haven't deleted or changed any files you didn't intend to. + 3. Push the branch to the repo by using the push_to_pull_request_branch tool from safeoutputs. diff --git a/.github/workflows/ubuntu-image-analyzer.lock.yml b/.github/workflows/ubuntu-image-analyzer.lock.yml index e1dc9da12b..26785513e3 100644 --- a/.github/workflows/ubuntu-image-analyzer.lock.yml +++ b/.github/workflows/ubuntu-image-analyzer.lock.yml @@ -113,7 +113,14 @@ jobs: Tools: create_pull_request, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** + + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. diff --git a/.github/workflows/unbloat-docs.lock.yml b/.github/workflows/unbloat-docs.lock.yml index db7ea9ac03..9c14e320ca 100644 --- a/.github/workflows/unbloat-docs.lock.yml +++ b/.github/workflows/unbloat-docs.lock.yml @@ -141,7 +141,14 @@ jobs: Tools: add_comment, create_pull_request, upload_asset, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** + + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). diff --git a/.github/workflows/weekly-editors-health-check.lock.yml b/.github/workflows/weekly-editors-health-check.lock.yml index c5cbdc4dd1..830d96973a 100644 --- a/.github/workflows/weekly-editors-health-check.lock.yml +++ b/.github/workflows/weekly-editors-health-check.lock.yml @@ -111,7 +111,14 @@ jobs: Tools: create_pull_request, upload_asset, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** + + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). diff --git a/.github/workflows/weekly-safe-outputs-spec-review.lock.yml b/.github/workflows/weekly-safe-outputs-spec-review.lock.yml index 2665b5638c..2d91bde797 100644 --- a/.github/workflows/weekly-safe-outputs-spec-review.lock.yml +++ b/.github/workflows/weekly-safe-outputs-spec-review.lock.yml @@ -110,7 +110,14 @@ jobs: Tools: create_pull_request, missing_tool, missing_data - create_pull_request: commit changes to a local branch (do not push), then call this tool from safeoutputs. + **Creating a Pull Request** + + To create a pull request: + 1. Make any file changes directly in the working directory. + 2. If you haven't done so already, create a local branch using an appropriate unique name. + 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. + 4. Do not push your changes. That will be done by the tool. + 5. Create the pull request with the create_pull_request tool from safeoutputs. diff --git a/pkg/workflow/unified_prompt_step.go b/pkg/workflow/unified_prompt_step.go index f6510a1fa3..a9e33f8beb 100644 --- a/pkg/workflow/unified_prompt_step.go +++ b/pkg/workflow/unified_prompt_step.go @@ -719,11 +719,21 @@ func generateSafeOutputsPerToolInstructions(b *strings.Builder, safeOutputs *Saf // Special multi-step instructions for complex tools if safeOutputs.CreatePullRequests != nil { - fmt.Fprintf(b, "create_pull_request: commit changes to a local branch (do not push), then call this tool from %s.\n\n", constants.SafeOutputsMCPServerID) + b.WriteString("**Creating a Pull Request**\n\n") + b.WriteString("To create a pull request:\n") + b.WriteString("1. Make any file changes directly in the working directory.\n") + b.WriteString("2. If you haven't done so already, create a local branch using an appropriate unique name.\n") + b.WriteString("3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to.\n") + b.WriteString("4. Do not push your changes. That will be done by the tool.\n") + fmt.Fprintf(b, "5. Create the pull request with the create_pull_request tool from %s.\n\n", constants.SafeOutputsMCPServerID) } if safeOutputs.PushToPullRequestBranch != nil { - fmt.Fprintf(b, "push_to_pull_request_branch: commit changes locally (do not push), then call this tool from %s.\n\n", constants.SafeOutputsMCPServerID) + b.WriteString("**Pushing Changes to a Pull Request Branch**\n\n") + b.WriteString("To push changes to the branch of a pull request:\n") + b.WriteString("1. Make any file changes directly in the working directory.\n") + b.WriteString("2. Add and commit your changes to the local copy of the pull request branch. Be careful to add exactly the files you intend, and verify you haven't deleted or changed any files you didn't intend to.\n") + fmt.Fprintf(b, "3. Push the branch to the repo by using the push_to_pull_request_branch tool from %s.\n\n", constants.SafeOutputsMCPServerID) } if safeOutputs.UploadAssets != nil { From 7f1f438c88b2d304125910cef20ac1d543af4dbd Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sun, 22 Feb 2026 20:25:06 +0000 Subject: [PATCH 5/7] Refactor safe outputs per-tool instructions to template files, remove spurious newlines Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- .../agent-performance-analyzer.lock.yml | 1 - .../workflows/agent-persona-explorer.lock.yml | 1 - .github/workflows/ai-moderator.lock.yml | 1 - .github/workflows/archie.lock.yml | 1 - .github/workflows/artifacts-summary.lock.yml | 1 - .github/workflows/audit-workflows.lock.yml | 1 - .github/workflows/auto-triage-issues.lock.yml | 1 - .github/workflows/blog-auditor.lock.yml | 1 - .github/workflows/bot-detection.lock.yml | 1 - .github/workflows/brave.lock.yml | 1 - .../breaking-change-checker.lock.yml | 1 - .github/workflows/changeset.lock.yml | 11 +-- .github/workflows/ci-coach.lock.yml | 13 +--- .github/workflows/ci-doctor.lock.yml | 1 - .../claude-code-user-docs-review.lock.yml | 1 - .../cli-consistency-checker.lock.yml | 1 - .../workflows/cli-version-checker.lock.yml | 1 - .github/workflows/cloclo.lock.yml | 13 +--- .../workflows/code-scanning-fixer.lock.yml | 13 +--- .github/workflows/code-simplifier.lock.yml | 13 +--- .../commit-changes-analyzer.lock.yml | 1 - .github/workflows/contribution-check.lock.yml | 1 - .../workflows/copilot-agent-analysis.lock.yml | 1 - .../copilot-cli-deep-research.lock.yml | 1 - .../copilot-pr-merged-report.lock.yml | 1 - .../copilot-pr-nlp-analysis.lock.yml | 1 - .../copilot-pr-prompt-analysis.lock.yml | 1 - .../copilot-session-insights.lock.yml | 1 - .github/workflows/craft.lock.yml | 11 +-- .../daily-assign-issue-to-user.lock.yml | 1 - .github/workflows/daily-choice-test.lock.yml | 1 - .../workflows/daily-cli-performance.lock.yml | 1 - .../workflows/daily-cli-tools-tester.lock.yml | 1 - .github/workflows/daily-code-metrics.lock.yml | 1 - .../workflows/daily-compiler-quality.lock.yml | 1 - .../daily-copilot-token-report.lock.yml | 1 - .github/workflows/daily-doc-updater.lock.yml | 13 +--- .github/workflows/daily-fact.lock.yml | 1 - .github/workflows/daily-file-diet.lock.yml | 1 - .../workflows/daily-firewall-report.lock.yml | 1 - .../workflows/daily-issues-report.lock.yml | 1 - .../daily-malicious-code-scan.lock.yml | 1 - .../daily-mcp-concurrency-analysis.lock.yml | 1 - .../daily-multi-device-docs-tester.lock.yml | 1 - .github/workflows/daily-news.lock.yml | 1 - .../daily-observability-report.lock.yml | 1 - .../daily-performance-summary.lock.yml | 1 - .github/workflows/daily-regulatory.lock.yml | 1 - .../daily-rendering-scripts-verifier.lock.yml | 13 +--- .../workflows/daily-repo-chronicle.lock.yml | 1 - .../daily-safe-output-optimizer.lock.yml | 1 - .../daily-safe-outputs-conformance.lock.yml | 1 - .../workflows/daily-secrets-analysis.lock.yml | 1 - .../daily-security-red-team.lock.yml | 1 - .github/workflows/daily-semgrep-scan.lock.yml | 1 - .../daily-syntax-error-quality.lock.yml | 1 - .../daily-team-evolution-insights.lock.yml | 1 - .github/workflows/daily-team-status.lock.yml | 1 - .../daily-testify-uber-super-expert.lock.yml | 1 - .../workflows/daily-workflow-updater.lock.yml | 13 +--- .github/workflows/deep-report.lock.yml | 1 - .github/workflows/delight.lock.yml | 1 - .github/workflows/dependabot-burner.lock.yml | 1 - .../workflows/dependabot-go-checker.lock.yml | 1 - .github/workflows/dev-hawk.lock.yml | 1 - .github/workflows/dev.lock.yml | 1 - .../developer-docs-consolidator.lock.yml | 13 +--- .github/workflows/dictation-prompt.lock.yml | 13 +--- .../workflows/discussion-task-miner.lock.yml | 1 - .github/workflows/docs-noob-tester.lock.yml | 1 - .github/workflows/draft-pr-cleanup.lock.yml | 1 - .../duplicate-code-detector.lock.yml | 1 - .../example-workflow-analyzer.lock.yml | 1 - .github/workflows/firewall-escape.lock.yml | 1 - .../workflows/functional-pragmatist.lock.yml | 13 +--- .../github-mcp-structural-analysis.lock.yml | 1 - .../github-mcp-tools-report.lock.yml | 13 +--- .../github-remote-mcp-auth-test.lock.yml | 1 - .../workflows/glossary-maintainer.lock.yml | 13 +--- .github/workflows/go-fan.lock.yml | 1 - .github/workflows/go-logger.lock.yml | 13 +--- .../workflows/go-pattern-detector.lock.yml | 1 - .github/workflows/gpclean.lock.yml | 1 - .github/workflows/grumpy-reviewer.lock.yml | 1 - .github/workflows/hourly-ci-cleaner.lock.yml | 13 +--- .../workflows/instructions-janitor.lock.yml | 13 +--- .github/workflows/issue-arborist.lock.yml | 1 - .github/workflows/issue-monster.lock.yml | 1 - .github/workflows/issue-triage-agent.lock.yml | 1 - .github/workflows/jsweep.lock.yml | 13 +--- .../workflows/layout-spec-maintainer.lock.yml | 13 +--- .github/workflows/lockfile-stats.lock.yml | 1 - .github/workflows/mcp-inspector.lock.yml | 1 - .github/workflows/mergefest.lock.yml | 11 +-- .../workflows/notion-issue-summary.lock.yml | 1 - .github/workflows/org-health-report.lock.yml | 1 - .github/workflows/pdf-summary.lock.yml | 1 - .github/workflows/plan.lock.yml | 1 - .github/workflows/poem-bot.lock.yml | 21 +----- .github/workflows/portfolio-analyst.lock.yml | 1 - .../workflows/pr-nitpick-reviewer.lock.yml | 1 - .github/workflows/pr-triage-agent.lock.yml | 1 - .../prompt-clustering-analysis.lock.yml | 1 - .github/workflows/python-data-charts.lock.yml | 1 - .github/workflows/q.lock.yml | 13 +--- .github/workflows/refiner.lock.yml | 13 +--- .github/workflows/release.lock.yml | 1 - .../workflows/repo-audit-analyzer.lock.yml | 1 - .github/workflows/repo-tree-map.lock.yml | 1 - .../repository-quality-improver.lock.yml | 1 - .github/workflows/research.lock.yml | 1 - .github/workflows/safe-output-health.lock.yml | 1 - .../schema-consistency-checker.lock.yml | 1 - .github/workflows/scout.lock.yml | 1 - .../workflows/security-compliance.lock.yml | 1 - .github/workflows/security-review.lock.yml | 1 - .../semantic-function-refactor.lock.yml | 1 - .github/workflows/sergo.lock.yml | 1 - .../workflows/slide-deck-maintainer.lock.yml | 13 +--- .github/workflows/smoke-agent.lock.yml | 1 - .github/workflows/smoke-claude.lock.yml | 11 +-- .github/workflows/smoke-codex.lock.yml | 1 - .github/workflows/smoke-copilot-arm.lock.yml | 1 - .github/workflows/smoke-copilot.lock.yml | 1 - .github/workflows/smoke-gemini.lock.yml | 1 - .github/workflows/smoke-multi-pr.lock.yml | 13 +--- .github/workflows/smoke-project.lock.yml | 13 +--- .github/workflows/smoke-temporary-id.lock.yml | 1 - .github/workflows/smoke-test-tools.lock.yml | 1 - .../workflows/stale-repo-identifier.lock.yml | 1 - .../workflows/static-analysis-report.lock.yml | 1 - .../workflows/step-name-alignment.lock.yml | 1 - .github/workflows/sub-issue-closer.lock.yml | 1 - .github/workflows/super-linter.lock.yml | 1 - .../workflows/technical-doc-writer.lock.yml | 13 +--- .github/workflows/terminal-stylist.lock.yml | 1 - .../test-create-pr-error-handling.lock.yml | 13 +--- .github/workflows/test-dispatcher.lock.yml | 1 - .../test-project-url-default.lock.yml | 1 - .github/workflows/tidy.lock.yml | 21 +----- .github/workflows/typist.lock.yml | 1 - .../workflows/ubuntu-image-analyzer.lock.yml | 13 +--- .github/workflows/unbloat-docs.lock.yml | 13 +--- .github/workflows/video-analyzer.lock.yml | 1 - .../weekly-editors-health-check.lock.yml | 13 +--- .../workflows/weekly-issue-summary.lock.yml | 1 - .../weekly-safe-outputs-spec-review.lock.yml | 13 +--- .github/workflows/workflow-generator.lock.yml | 1 - .../workflow-health-manager.lock.yml | 1 - .../workflows/workflow-normalizer.lock.yml | 1 - .../workflow-skill-extractor.lock.yml | 1 - .../md/safe_outputs_auto_create_issue.md | 2 + .../md/safe_outputs_create_pull_request.md | 9 +++ .../md/safe_outputs_push_to_pr_branch.md | 7 ++ .../safe_outputs_default_create_issue_test.go | 24 +++--- pkg/workflow/sh.go | 25 ++++--- pkg/workflow/unified_prompt_step.go | 73 +++++++++---------- 157 files changed, 185 insertions(+), 522 deletions(-) create mode 100644 actions/setup/md/safe_outputs_auto_create_issue.md create mode 100644 actions/setup/md/safe_outputs_create_pull_request.md create mode 100644 actions/setup/md/safe_outputs_push_to_pr_branch.md diff --git a/.github/workflows/agent-performance-analyzer.lock.yml b/.github/workflows/agent-performance-analyzer.lock.yml index a7b59f77b2..1353e85d5b 100644 --- a/.github/workflows/agent-performance-analyzer.lock.yml +++ b/.github/workflows/agent-performance-analyzer.lock.yml @@ -116,7 +116,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, create_issue, create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/agent-persona-explorer.lock.yml b/.github/workflows/agent-persona-explorer.lock.yml index bfbc22216c..91bc9cd3df 100644 --- a/.github/workflows/agent-persona-explorer.lock.yml +++ b/.github/workflows/agent-persona-explorer.lock.yml @@ -116,7 +116,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/ai-moderator.lock.yml b/.github/workflows/ai-moderator.lock.yml index 25602c353c..fd2d6e8541 100644 --- a/.github/workflows/ai-moderator.lock.yml +++ b/.github/workflows/ai-moderator.lock.yml @@ -153,7 +153,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_labels, hide_comment, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/archie.lock.yml b/.github/workflows/archie.lock.yml index 7030015d55..374124d46a 100644 --- a/.github/workflows/archie.lock.yml +++ b/.github/workflows/archie.lock.yml @@ -146,7 +146,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/artifacts-summary.lock.yml b/.github/workflows/artifacts-summary.lock.yml index 37534ddda3..01a8a2298d 100644 --- a/.github/workflows/artifacts-summary.lock.yml +++ b/.github/workflows/artifacts-summary.lock.yml @@ -114,7 +114,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/audit-workflows.lock.yml b/.github/workflows/audit-workflows.lock.yml index fb437ca3f1..f2966f1e22 100644 --- a/.github/workflows/audit-workflows.lock.yml +++ b/.github/workflows/audit-workflows.lock.yml @@ -119,7 +119,6 @@ jobs: Tools: create_discussion, upload_asset, missing_tool, missing_data upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/auto-triage-issues.lock.yml b/.github/workflows/auto-triage-issues.lock.yml index d4c9bd875a..2c317e8da8 100644 --- a/.github/workflows/auto-triage-issues.lock.yml +++ b/.github/workflows/auto-triage-issues.lock.yml @@ -131,7 +131,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, add_labels, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/blog-auditor.lock.yml b/.github/workflows/blog-auditor.lock.yml index cad7f9a037..0f2dbbede3 100644 --- a/.github/workflows/blog-auditor.lock.yml +++ b/.github/workflows/blog-auditor.lock.yml @@ -115,7 +115,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/bot-detection.lock.yml b/.github/workflows/bot-detection.lock.yml index a9f04d7cb2..9ecb531851 100644 --- a/.github/workflows/bot-detection.lock.yml +++ b/.github/workflows/bot-detection.lock.yml @@ -114,7 +114,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, update_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/brave.lock.yml b/.github/workflows/brave.lock.yml index bb81591cbe..2468fac61f 100644 --- a/.github/workflows/brave.lock.yml +++ b/.github/workflows/brave.lock.yml @@ -136,7 +136,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/breaking-change-checker.lock.yml b/.github/workflows/breaking-change-checker.lock.yml index f61c6bd77c..ba541b172e 100644 --- a/.github/workflows/breaking-change-checker.lock.yml +++ b/.github/workflows/breaking-change-checker.lock.yml @@ -115,7 +115,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/changeset.lock.yml b/.github/workflows/changeset.lock.yml index ec5bb6303d..b7d1b401f1 100644 --- a/.github/workflows/changeset.lock.yml +++ b/.github/workflows/changeset.lock.yml @@ -142,14 +142,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: update_pull_request, push_to_pull_request_branch, missing_tool, missing_data - - **Pushing Changes to a Pull Request Branch** - - To push changes to the branch of a pull request: - 1. Make any file changes directly in the working directory. - 2. Add and commit your changes to the local copy of the pull request branch. Be careful to add exactly the files you intend, and verify you haven't deleted or changed any files you didn't intend to. - 3. Push the branch to the repo by using the push_to_pull_request_branch tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_push_to_pr_branch.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/ci-coach.lock.yml b/.github/workflows/ci-coach.lock.yml index dbe52df018..fd2a7d72b9 100644 --- a/.github/workflows/ci-coach.lock.yml +++ b/.github/workflows/ci-coach.lock.yml @@ -117,16 +117,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_pull_request, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/ci-doctor.lock.yml b/.github/workflows/ci-doctor.lock.yml index 0d0ce319d9..b16f8ef6ea 100644 --- a/.github/workflows/ci-doctor.lock.yml +++ b/.github/workflows/ci-doctor.lock.yml @@ -130,7 +130,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, create_issue, update_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/claude-code-user-docs-review.lock.yml b/.github/workflows/claude-code-user-docs-review.lock.yml index d5f7ae56c5..925a763646 100644 --- a/.github/workflows/claude-code-user-docs-review.lock.yml +++ b/.github/workflows/claude-code-user-docs-review.lock.yml @@ -110,7 +110,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/cli-consistency-checker.lock.yml b/.github/workflows/cli-consistency-checker.lock.yml index 91b626ccda..54e6edd886 100644 --- a/.github/workflows/cli-consistency-checker.lock.yml +++ b/.github/workflows/cli-consistency-checker.lock.yml @@ -108,7 +108,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/cli-version-checker.lock.yml b/.github/workflows/cli-version-checker.lock.yml index 336cbbb7a1..a22333df7f 100644 --- a/.github/workflows/cli-version-checker.lock.yml +++ b/.github/workflows/cli-version-checker.lock.yml @@ -115,7 +115,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/cloclo.lock.yml b/.github/workflows/cloclo.lock.yml index e664a98367..14e3147050 100644 --- a/.github/workflows/cloclo.lock.yml +++ b/.github/workflows/cloclo.lock.yml @@ -177,16 +177,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, create_pull_request, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/code-scanning-fixer.lock.yml b/.github/workflows/code-scanning-fixer.lock.yml index 8834163b32..ed4b6e01db 100644 --- a/.github/workflows/code-scanning-fixer.lock.yml +++ b/.github/workflows/code-scanning-fixer.lock.yml @@ -111,16 +111,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_pull_request, add_labels, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/code-simplifier.lock.yml b/.github/workflows/code-simplifier.lock.yml index 2b4470ee2f..c30567f096 100644 --- a/.github/workflows/code-simplifier.lock.yml +++ b/.github/workflows/code-simplifier.lock.yml @@ -116,16 +116,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_pull_request, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/commit-changes-analyzer.lock.yml b/.github/workflows/commit-changes-analyzer.lock.yml index 4a52a0634a..fb9cc527f7 100644 --- a/.github/workflows/commit-changes-analyzer.lock.yml +++ b/.github/workflows/commit-changes-analyzer.lock.yml @@ -116,7 +116,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/contribution-check.lock.yml b/.github/workflows/contribution-check.lock.yml index cc5ccbf9bf..d18d3d8d20 100644 --- a/.github/workflows/contribution-check.lock.yml +++ b/.github/workflows/contribution-check.lock.yml @@ -112,7 +112,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, create_issue, add_labels, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/copilot-agent-analysis.lock.yml b/.github/workflows/copilot-agent-analysis.lock.yml index 095a76d587..cc3b9cffe8 100644 --- a/.github/workflows/copilot-agent-analysis.lock.yml +++ b/.github/workflows/copilot-agent-analysis.lock.yml @@ -117,7 +117,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/copilot-cli-deep-research.lock.yml b/.github/workflows/copilot-cli-deep-research.lock.yml index 68210f3632..bc83264a5a 100644 --- a/.github/workflows/copilot-cli-deep-research.lock.yml +++ b/.github/workflows/copilot-cli-deep-research.lock.yml @@ -114,7 +114,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/copilot-pr-merged-report.lock.yml b/.github/workflows/copilot-pr-merged-report.lock.yml index e42ecca79b..fb2284154b 100644 --- a/.github/workflows/copilot-pr-merged-report.lock.yml +++ b/.github/workflows/copilot-pr-merged-report.lock.yml @@ -107,7 +107,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, missing_tool, missing_data - GH_AW_PROMPT_EOF cat << 'GH_AW_PROMPT_EOF' diff --git a/.github/workflows/copilot-pr-nlp-analysis.lock.yml b/.github/workflows/copilot-pr-nlp-analysis.lock.yml index 7069bfb624..ddc1e67648 100644 --- a/.github/workflows/copilot-pr-nlp-analysis.lock.yml +++ b/.github/workflows/copilot-pr-nlp-analysis.lock.yml @@ -119,7 +119,6 @@ jobs: Tools: create_discussion, upload_asset, missing_tool, missing_data upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/copilot-pr-prompt-analysis.lock.yml b/.github/workflows/copilot-pr-prompt-analysis.lock.yml index 799893225c..0aae6cef76 100644 --- a/.github/workflows/copilot-pr-prompt-analysis.lock.yml +++ b/.github/workflows/copilot-pr-prompt-analysis.lock.yml @@ -117,7 +117,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/copilot-session-insights.lock.yml b/.github/workflows/copilot-session-insights.lock.yml index ff79d62845..67e95691c0 100644 --- a/.github/workflows/copilot-session-insights.lock.yml +++ b/.github/workflows/copilot-session-insights.lock.yml @@ -123,7 +123,6 @@ jobs: Tools: create_discussion, upload_asset, missing_tool, missing_data upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/craft.lock.yml b/.github/workflows/craft.lock.yml index bc5db41bdc..4ff1a3d405 100644 --- a/.github/workflows/craft.lock.yml +++ b/.github/workflows/craft.lock.yml @@ -132,14 +132,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, push_to_pull_request_branch, missing_tool, missing_data - - **Pushing Changes to a Pull Request Branch** - - To push changes to the branch of a pull request: - 1. Make any file changes directly in the working directory. - 2. Add and commit your changes to the local copy of the pull request branch. Be careful to add exactly the files you intend, and verify you haven't deleted or changed any files you didn't intend to. - 3. Push the branch to the repo by using the push_to_pull_request_branch tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_push_to_pr_branch.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-assign-issue-to-user.lock.yml b/.github/workflows/daily-assign-issue-to-user.lock.yml index 2ac36786d1..c25320f386 100644 --- a/.github/workflows/daily-assign-issue-to-user.lock.yml +++ b/.github/workflows/daily-assign-issue-to-user.lock.yml @@ -108,7 +108,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, assign_to_user, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-choice-test.lock.yml b/.github/workflows/daily-choice-test.lock.yml index 591e1fbd2a..501480402f 100644 --- a/.github/workflows/daily-choice-test.lock.yml +++ b/.github/workflows/daily-choice-test.lock.yml @@ -108,7 +108,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-cli-performance.lock.yml b/.github/workflows/daily-cli-performance.lock.yml index 1246102449..af6fc255a0 100644 --- a/.github/workflows/daily-cli-performance.lock.yml +++ b/.github/workflows/daily-cli-performance.lock.yml @@ -116,7 +116,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, create_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-cli-tools-tester.lock.yml b/.github/workflows/daily-cli-tools-tester.lock.yml index 7bfb45e62e..4762936698 100644 --- a/.github/workflows/daily-cli-tools-tester.lock.yml +++ b/.github/workflows/daily-cli-tools-tester.lock.yml @@ -109,7 +109,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-code-metrics.lock.yml b/.github/workflows/daily-code-metrics.lock.yml index a3570bd182..435df4738f 100644 --- a/.github/workflows/daily-code-metrics.lock.yml +++ b/.github/workflows/daily-code-metrics.lock.yml @@ -119,7 +119,6 @@ jobs: Tools: create_discussion, upload_asset, missing_tool, missing_data upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-compiler-quality.lock.yml b/.github/workflows/daily-compiler-quality.lock.yml index 4f2a240b9d..a176576a56 100644 --- a/.github/workflows/daily-compiler-quality.lock.yml +++ b/.github/workflows/daily-compiler-quality.lock.yml @@ -114,7 +114,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-copilot-token-report.lock.yml b/.github/workflows/daily-copilot-token-report.lock.yml index f8dc10ae23..7f244d60ca 100644 --- a/.github/workflows/daily-copilot-token-report.lock.yml +++ b/.github/workflows/daily-copilot-token-report.lock.yml @@ -118,7 +118,6 @@ jobs: Tools: create_discussion, upload_asset, missing_tool, missing_data upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-doc-updater.lock.yml b/.github/workflows/daily-doc-updater.lock.yml index 8ad52c24a9..0c94fc8111 100644 --- a/.github/workflows/daily-doc-updater.lock.yml +++ b/.github/workflows/daily-doc-updater.lock.yml @@ -110,16 +110,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_pull_request, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-fact.lock.yml b/.github/workflows/daily-fact.lock.yml index 4ff55eb9bf..c6ac95fad9 100644 --- a/.github/workflows/daily-fact.lock.yml +++ b/.github/workflows/daily-fact.lock.yml @@ -94,7 +94,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-file-diet.lock.yml b/.github/workflows/daily-file-diet.lock.yml index 9c6ca9cbb8..0028663ec5 100644 --- a/.github/workflows/daily-file-diet.lock.yml +++ b/.github/workflows/daily-file-diet.lock.yml @@ -116,7 +116,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-firewall-report.lock.yml b/.github/workflows/daily-firewall-report.lock.yml index 0f6afd3752..3288450e1a 100644 --- a/.github/workflows/daily-firewall-report.lock.yml +++ b/.github/workflows/daily-firewall-report.lock.yml @@ -117,7 +117,6 @@ jobs: Tools: create_discussion, upload_asset, missing_tool, missing_data upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-issues-report.lock.yml b/.github/workflows/daily-issues-report.lock.yml index 20c213ea91..52ed8fde5e 100644 --- a/.github/workflows/daily-issues-report.lock.yml +++ b/.github/workflows/daily-issues-report.lock.yml @@ -122,7 +122,6 @@ jobs: Tools: create_discussion, close_discussion, upload_asset, missing_tool, missing_data upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-malicious-code-scan.lock.yml b/.github/workflows/daily-malicious-code-scan.lock.yml index 5251029b0e..3ccaba1af8 100644 --- a/.github/workflows/daily-malicious-code-scan.lock.yml +++ b/.github/workflows/daily-malicious-code-scan.lock.yml @@ -113,7 +113,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_code_scanning_alert, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-mcp-concurrency-analysis.lock.yml b/.github/workflows/daily-mcp-concurrency-analysis.lock.yml index fc4ef7cd73..c210e22b5b 100644 --- a/.github/workflows/daily-mcp-concurrency-analysis.lock.yml +++ b/.github/workflows/daily-mcp-concurrency-analysis.lock.yml @@ -114,7 +114,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, create_agent_session, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-multi-device-docs-tester.lock.yml b/.github/workflows/daily-multi-device-docs-tester.lock.yml index d3acf9cb8b..e26509a833 100644 --- a/.github/workflows/daily-multi-device-docs-tester.lock.yml +++ b/.github/workflows/daily-multi-device-docs-tester.lock.yml @@ -123,7 +123,6 @@ jobs: Tools: create_issue, upload_asset, missing_tool, missing_data upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-news.lock.yml b/.github/workflows/daily-news.lock.yml index 1d93558859..3b2c961d9a 100644 --- a/.github/workflows/daily-news.lock.yml +++ b/.github/workflows/daily-news.lock.yml @@ -120,7 +120,6 @@ jobs: Tools: create_discussion, upload_asset, missing_tool, missing_data upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-observability-report.lock.yml b/.github/workflows/daily-observability-report.lock.yml index 9458bd9846..7d5dc7e0e7 100644 --- a/.github/workflows/daily-observability-report.lock.yml +++ b/.github/workflows/daily-observability-report.lock.yml @@ -115,7 +115,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, close_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-performance-summary.lock.yml b/.github/workflows/daily-performance-summary.lock.yml index f89eb23bd7..6531607fb3 100644 --- a/.github/workflows/daily-performance-summary.lock.yml +++ b/.github/workflows/daily-performance-summary.lock.yml @@ -118,7 +118,6 @@ jobs: Tools: create_discussion, close_discussion, upload_asset, missing_tool, missing_data upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-regulatory.lock.yml b/.github/workflows/daily-regulatory.lock.yml index 33a9b7ff41..e70c95f528 100644 --- a/.github/workflows/daily-regulatory.lock.yml +++ b/.github/workflows/daily-regulatory.lock.yml @@ -114,7 +114,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, close_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-rendering-scripts-verifier.lock.yml b/.github/workflows/daily-rendering-scripts-verifier.lock.yml index 7829e2fb70..eced6d180f 100644 --- a/.github/workflows/daily-rendering-scripts-verifier.lock.yml +++ b/.github/workflows/daily-rendering-scripts-verifier.lock.yml @@ -117,16 +117,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_pull_request, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-repo-chronicle.lock.yml b/.github/workflows/daily-repo-chronicle.lock.yml index 075c6bfa05..87e7cb40a6 100644 --- a/.github/workflows/daily-repo-chronicle.lock.yml +++ b/.github/workflows/daily-repo-chronicle.lock.yml @@ -117,7 +117,6 @@ jobs: Tools: create_discussion, upload_asset, missing_tool, missing_data upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-safe-output-optimizer.lock.yml b/.github/workflows/daily-safe-output-optimizer.lock.yml index 8d67b4963d..2cecdd8ac4 100644 --- a/.github/workflows/daily-safe-output-optimizer.lock.yml +++ b/.github/workflows/daily-safe-output-optimizer.lock.yml @@ -118,7 +118,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-safe-outputs-conformance.lock.yml b/.github/workflows/daily-safe-outputs-conformance.lock.yml index 7aa0ed30b9..7732e2e835 100644 --- a/.github/workflows/daily-safe-outputs-conformance.lock.yml +++ b/.github/workflows/daily-safe-outputs-conformance.lock.yml @@ -113,7 +113,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-secrets-analysis.lock.yml b/.github/workflows/daily-secrets-analysis.lock.yml index ca3b8facda..c48ceddab0 100644 --- a/.github/workflows/daily-secrets-analysis.lock.yml +++ b/.github/workflows/daily-secrets-analysis.lock.yml @@ -113,7 +113,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, close_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-security-red-team.lock.yml b/.github/workflows/daily-security-red-team.lock.yml index 61605d4b7a..0da09079bc 100644 --- a/.github/workflows/daily-security-red-team.lock.yml +++ b/.github/workflows/daily-security-red-team.lock.yml @@ -114,7 +114,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-semgrep-scan.lock.yml b/.github/workflows/daily-semgrep-scan.lock.yml index 8a8e913ece..7d1b06aded 100644 --- a/.github/workflows/daily-semgrep-scan.lock.yml +++ b/.github/workflows/daily-semgrep-scan.lock.yml @@ -113,7 +113,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_code_scanning_alert, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-syntax-error-quality.lock.yml b/.github/workflows/daily-syntax-error-quality.lock.yml index 72da1629f5..01cfabc627 100644 --- a/.github/workflows/daily-syntax-error-quality.lock.yml +++ b/.github/workflows/daily-syntax-error-quality.lock.yml @@ -113,7 +113,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-team-evolution-insights.lock.yml b/.github/workflows/daily-team-evolution-insights.lock.yml index 1fd70d3730..1554d58fbc 100644 --- a/.github/workflows/daily-team-evolution-insights.lock.yml +++ b/.github/workflows/daily-team-evolution-insights.lock.yml @@ -113,7 +113,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-team-status.lock.yml b/.github/workflows/daily-team-status.lock.yml index 2fa71f0a7f..4a732eb9db 100644 --- a/.github/workflows/daily-team-status.lock.yml +++ b/.github/workflows/daily-team-status.lock.yml @@ -122,7 +122,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-testify-uber-super-expert.lock.yml b/.github/workflows/daily-testify-uber-super-expert.lock.yml index 5e87bd1b6b..61d93c2ff2 100644 --- a/.github/workflows/daily-testify-uber-super-expert.lock.yml +++ b/.github/workflows/daily-testify-uber-super-expert.lock.yml @@ -118,7 +118,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/daily-workflow-updater.lock.yml b/.github/workflows/daily-workflow-updater.lock.yml index 37deec6ab3..5d9435719f 100644 --- a/.github/workflows/daily-workflow-updater.lock.yml +++ b/.github/workflows/daily-workflow-updater.lock.yml @@ -109,16 +109,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_pull_request, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/deep-report.lock.yml b/.github/workflows/deep-report.lock.yml index 0b2ef30337..cb470679d6 100644 --- a/.github/workflows/deep-report.lock.yml +++ b/.github/workflows/deep-report.lock.yml @@ -118,7 +118,6 @@ jobs: Tools: create_issue, create_discussion, upload_asset, missing_tool, missing_data upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/delight.lock.yml b/.github/workflows/delight.lock.yml index 326889d3d3..ad1224df7c 100644 --- a/.github/workflows/delight.lock.yml +++ b/.github/workflows/delight.lock.yml @@ -115,7 +115,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/dependabot-burner.lock.yml b/.github/workflows/dependabot-burner.lock.yml index ef554c6293..6210c91721 100644 --- a/.github/workflows/dependabot-burner.lock.yml +++ b/.github/workflows/dependabot-burner.lock.yml @@ -110,7 +110,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/dependabot-go-checker.lock.yml b/.github/workflows/dependabot-go-checker.lock.yml index ad412daf0b..0054d7ff58 100644 --- a/.github/workflows/dependabot-go-checker.lock.yml +++ b/.github/workflows/dependabot-go-checker.lock.yml @@ -108,7 +108,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, close_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/dev-hawk.lock.yml b/.github/workflows/dev-hawk.lock.yml index bcf5261896..079e02f07b 100644 --- a/.github/workflows/dev-hawk.lock.yml +++ b/.github/workflows/dev-hawk.lock.yml @@ -125,7 +125,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/dev.lock.yml b/.github/workflows/dev.lock.yml index c60d2661d2..7797ff87ad 100644 --- a/.github/workflows/dev.lock.yml +++ b/.github/workflows/dev.lock.yml @@ -108,7 +108,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/developer-docs-consolidator.lock.yml b/.github/workflows/developer-docs-consolidator.lock.yml index 72aa0cf736..1cd0de05f9 100644 --- a/.github/workflows/developer-docs-consolidator.lock.yml +++ b/.github/workflows/developer-docs-consolidator.lock.yml @@ -114,16 +114,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, create_pull_request, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/dictation-prompt.lock.yml b/.github/workflows/dictation-prompt.lock.yml index c01cad62d6..a5f7e2a120 100644 --- a/.github/workflows/dictation-prompt.lock.yml +++ b/.github/workflows/dictation-prompt.lock.yml @@ -112,16 +112,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_pull_request, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/discussion-task-miner.lock.yml b/.github/workflows/discussion-task-miner.lock.yml index 3a1f4cc22a..2bedbbc94c 100644 --- a/.github/workflows/discussion-task-miner.lock.yml +++ b/.github/workflows/discussion-task-miner.lock.yml @@ -115,7 +115,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, create_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/docs-noob-tester.lock.yml b/.github/workflows/docs-noob-tester.lock.yml index 7b7db54205..f4f1bcd8e3 100644 --- a/.github/workflows/docs-noob-tester.lock.yml +++ b/.github/workflows/docs-noob-tester.lock.yml @@ -116,7 +116,6 @@ jobs: Tools: create_discussion, upload_asset, missing_tool, missing_data upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/draft-pr-cleanup.lock.yml b/.github/workflows/draft-pr-cleanup.lock.yml index 498cf2e318..d9cc3621cb 100644 --- a/.github/workflows/draft-pr-cleanup.lock.yml +++ b/.github/workflows/draft-pr-cleanup.lock.yml @@ -109,7 +109,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, close_pull_request, add_labels, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/duplicate-code-detector.lock.yml b/.github/workflows/duplicate-code-detector.lock.yml index 761ab1c919..b206f96878 100644 --- a/.github/workflows/duplicate-code-detector.lock.yml +++ b/.github/workflows/duplicate-code-detector.lock.yml @@ -110,7 +110,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/example-workflow-analyzer.lock.yml b/.github/workflows/example-workflow-analyzer.lock.yml index cd65c8e591..5fc415e46f 100644 --- a/.github/workflows/example-workflow-analyzer.lock.yml +++ b/.github/workflows/example-workflow-analyzer.lock.yml @@ -113,7 +113,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/firewall-escape.lock.yml b/.github/workflows/firewall-escape.lock.yml index 0b40490da4..9612a9955a 100644 --- a/.github/workflows/firewall-escape.lock.yml +++ b/.github/workflows/firewall-escape.lock.yml @@ -133,7 +133,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/functional-pragmatist.lock.yml b/.github/workflows/functional-pragmatist.lock.yml index 9885663e71..65bf9aec94 100644 --- a/.github/workflows/functional-pragmatist.lock.yml +++ b/.github/workflows/functional-pragmatist.lock.yml @@ -112,16 +112,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_pull_request, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/github-mcp-structural-analysis.lock.yml b/.github/workflows/github-mcp-structural-analysis.lock.yml index 898c03a0cf..efe6d290ff 100644 --- a/.github/workflows/github-mcp-structural-analysis.lock.yml +++ b/.github/workflows/github-mcp-structural-analysis.lock.yml @@ -116,7 +116,6 @@ jobs: Tools: create_discussion, upload_asset, missing_tool, missing_data upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/github-mcp-tools-report.lock.yml b/.github/workflows/github-mcp-tools-report.lock.yml index 4aa0a62cd4..755ec3d332 100644 --- a/.github/workflows/github-mcp-tools-report.lock.yml +++ b/.github/workflows/github-mcp-tools-report.lock.yml @@ -114,16 +114,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, create_pull_request, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/github-remote-mcp-auth-test.lock.yml b/.github/workflows/github-remote-mcp-auth-test.lock.yml index 1f13745ade..85f1a187bd 100644 --- a/.github/workflows/github-remote-mcp-auth-test.lock.yml +++ b/.github/workflows/github-remote-mcp-auth-test.lock.yml @@ -110,7 +110,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/glossary-maintainer.lock.yml b/.github/workflows/glossary-maintainer.lock.yml index fa9e864ab1..0173c9179b 100644 --- a/.github/workflows/glossary-maintainer.lock.yml +++ b/.github/workflows/glossary-maintainer.lock.yml @@ -114,16 +114,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_pull_request, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/go-fan.lock.yml b/.github/workflows/go-fan.lock.yml index 3b436b9a1f..0c201e33bb 100644 --- a/.github/workflows/go-fan.lock.yml +++ b/.github/workflows/go-fan.lock.yml @@ -113,7 +113,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/go-logger.lock.yml b/.github/workflows/go-logger.lock.yml index adba9b7355..3df4900213 100644 --- a/.github/workflows/go-logger.lock.yml +++ b/.github/workflows/go-logger.lock.yml @@ -114,16 +114,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_pull_request, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/go-pattern-detector.lock.yml b/.github/workflows/go-pattern-detector.lock.yml index 9b804a6b61..9a19cde1b0 100644 --- a/.github/workflows/go-pattern-detector.lock.yml +++ b/.github/workflows/go-pattern-detector.lock.yml @@ -113,7 +113,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/gpclean.lock.yml b/.github/workflows/gpclean.lock.yml index a9a668ab43..610b758677 100644 --- a/.github/workflows/gpclean.lock.yml +++ b/.github/workflows/gpclean.lock.yml @@ -110,7 +110,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/grumpy-reviewer.lock.yml b/.github/workflows/grumpy-reviewer.lock.yml index 340c407cc6..0cea652588 100644 --- a/.github/workflows/grumpy-reviewer.lock.yml +++ b/.github/workflows/grumpy-reviewer.lock.yml @@ -137,7 +137,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_pull_request_review_comment, submit_pull_request_review, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/hourly-ci-cleaner.lock.yml b/.github/workflows/hourly-ci-cleaner.lock.yml index b2abcca2f8..4a49fe00be 100644 --- a/.github/workflows/hourly-ci-cleaner.lock.yml +++ b/.github/workflows/hourly-ci-cleaner.lock.yml @@ -117,16 +117,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_pull_request, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/instructions-janitor.lock.yml b/.github/workflows/instructions-janitor.lock.yml index d4d152eb9e..76081134fd 100644 --- a/.github/workflows/instructions-janitor.lock.yml +++ b/.github/workflows/instructions-janitor.lock.yml @@ -110,16 +110,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_pull_request, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/issue-arborist.lock.yml b/.github/workflows/issue-arborist.lock.yml index 886e229267..22e82231f2 100644 --- a/.github/workflows/issue-arborist.lock.yml +++ b/.github/workflows/issue-arborist.lock.yml @@ -113,7 +113,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, create_discussion, link_sub_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/issue-monster.lock.yml b/.github/workflows/issue-monster.lock.yml index 06893733ea..7269e79a56 100644 --- a/.github/workflows/issue-monster.lock.yml +++ b/.github/workflows/issue-monster.lock.yml @@ -120,7 +120,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, assign_to_agent, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/issue-triage-agent.lock.yml b/.github/workflows/issue-triage-agent.lock.yml index 4881caca7a..ece93e2040 100644 --- a/.github/workflows/issue-triage-agent.lock.yml +++ b/.github/workflows/issue-triage-agent.lock.yml @@ -103,7 +103,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, add_labels, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/jsweep.lock.yml b/.github/workflows/jsweep.lock.yml index 8e3f100a72..b13d4f5c14 100644 --- a/.github/workflows/jsweep.lock.yml +++ b/.github/workflows/jsweep.lock.yml @@ -110,16 +110,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_pull_request, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/layout-spec-maintainer.lock.yml b/.github/workflows/layout-spec-maintainer.lock.yml index bff19ccc0b..028b1036d6 100644 --- a/.github/workflows/layout-spec-maintainer.lock.yml +++ b/.github/workflows/layout-spec-maintainer.lock.yml @@ -110,16 +110,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_pull_request, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/lockfile-stats.lock.yml b/.github/workflows/lockfile-stats.lock.yml index a577879e4a..4fbd8b07fd 100644 --- a/.github/workflows/lockfile-stats.lock.yml +++ b/.github/workflows/lockfile-stats.lock.yml @@ -114,7 +114,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/mcp-inspector.lock.yml b/.github/workflows/mcp-inspector.lock.yml index 93dbc4701d..23b51efff4 100644 --- a/.github/workflows/mcp-inspector.lock.yml +++ b/.github/workflows/mcp-inspector.lock.yml @@ -128,7 +128,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/mergefest.lock.yml b/.github/workflows/mergefest.lock.yml index 16abb448cb..1a5067515c 100644 --- a/.github/workflows/mergefest.lock.yml +++ b/.github/workflows/mergefest.lock.yml @@ -130,14 +130,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: push_to_pull_request_branch, missing_tool, missing_data - - **Pushing Changes to a Pull Request Branch** - - To push changes to the branch of a pull request: - 1. Make any file changes directly in the working directory. - 2. Add and commit your changes to the local copy of the pull request branch. Be careful to add exactly the files you intend, and verify you haven't deleted or changed any files you didn't intend to. - 3. Push the branch to the repo by using the push_to_pull_request_branch tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_push_to_pr_branch.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/notion-issue-summary.lock.yml b/.github/workflows/notion-issue-summary.lock.yml index e8e24363ac..8e7803d8a5 100644 --- a/.github/workflows/notion-issue-summary.lock.yml +++ b/.github/workflows/notion-issue-summary.lock.yml @@ -116,7 +116,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/org-health-report.lock.yml b/.github/workflows/org-health-report.lock.yml index 0013e561da..e8e0c26108 100644 --- a/.github/workflows/org-health-report.lock.yml +++ b/.github/workflows/org-health-report.lock.yml @@ -118,7 +118,6 @@ jobs: Tools: create_discussion, upload_asset, missing_tool, missing_data upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/pdf-summary.lock.yml b/.github/workflows/pdf-summary.lock.yml index 45b90a2c3e..3e496254f2 100644 --- a/.github/workflows/pdf-summary.lock.yml +++ b/.github/workflows/pdf-summary.lock.yml @@ -158,7 +158,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/plan.lock.yml b/.github/workflows/plan.lock.yml index 8c7303e75f..8075785c64 100644 --- a/.github/workflows/plan.lock.yml +++ b/.github/workflows/plan.lock.yml @@ -136,7 +136,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, close_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/poem-bot.lock.yml b/.github/workflows/poem-bot.lock.yml index 32b16a7858..17d29959fa 100644 --- a/.github/workflows/poem-bot.lock.yml +++ b/.github/workflows/poem-bot.lock.yml @@ -148,25 +148,12 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, create_issue, update_issue, create_discussion, create_agent_session, create_pull_request, close_pull_request, create_pull_request_review_comment, add_labels, push_to_pull_request_branch, upload_asset, link_sub_issue, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Pushing Changes to a Pull Request Branch** - - To push changes to the branch of a pull request: - 1. Make any file changes directly in the working directory. - 2. Add and commit your changes to the local copy of the pull request branch. Be careful to add exactly the files you intend, and verify you haven't deleted or changed any files you didn't intend to. - 3. Push the branch to the repo by using the push_to_pull_request_branch tool from safeoutputs. + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat "/opt/gh-aw/prompts/safe_outputs_push_to_pr_branch.md" + cat << 'GH_AW_PROMPT_EOF' upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/portfolio-analyst.lock.yml b/.github/workflows/portfolio-analyst.lock.yml index 538e5050bb..266741e5bc 100644 --- a/.github/workflows/portfolio-analyst.lock.yml +++ b/.github/workflows/portfolio-analyst.lock.yml @@ -118,7 +118,6 @@ jobs: Tools: create_discussion, upload_asset, missing_tool, missing_data upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/pr-nitpick-reviewer.lock.yml b/.github/workflows/pr-nitpick-reviewer.lock.yml index 7410b73134..138e40b66c 100644 --- a/.github/workflows/pr-nitpick-reviewer.lock.yml +++ b/.github/workflows/pr-nitpick-reviewer.lock.yml @@ -165,7 +165,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, create_pull_request_review_comment, submit_pull_request_review, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/pr-triage-agent.lock.yml b/.github/workflows/pr-triage-agent.lock.yml index c68012f607..600807c834 100644 --- a/.github/workflows/pr-triage-agent.lock.yml +++ b/.github/workflows/pr-triage-agent.lock.yml @@ -109,7 +109,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, create_issue, add_labels, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/prompt-clustering-analysis.lock.yml b/.github/workflows/prompt-clustering-analysis.lock.yml index 554101f0ee..78c335282f 100644 --- a/.github/workflows/prompt-clustering-analysis.lock.yml +++ b/.github/workflows/prompt-clustering-analysis.lock.yml @@ -119,7 +119,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/python-data-charts.lock.yml b/.github/workflows/python-data-charts.lock.yml index b9f0d5740e..1237c21e43 100644 --- a/.github/workflows/python-data-charts.lock.yml +++ b/.github/workflows/python-data-charts.lock.yml @@ -115,7 +115,6 @@ jobs: Tools: create_discussion, upload_asset, missing_tool, missing_data upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/q.lock.yml b/.github/workflows/q.lock.yml index 9dd7c1e74d..b59eefeb5c 100644 --- a/.github/workflows/q.lock.yml +++ b/.github/workflows/q.lock.yml @@ -170,16 +170,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, create_pull_request, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/refiner.lock.yml b/.github/workflows/refiner.lock.yml index 4e57b3f6dc..0b77b88977 100644 --- a/.github/workflows/refiner.lock.yml +++ b/.github/workflows/refiner.lock.yml @@ -134,16 +134,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, create_pull_request, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/release.lock.yml b/.github/workflows/release.lock.yml index fa03f977d3..6cea878780 100644 --- a/.github/workflows/release.lock.yml +++ b/.github/workflows/release.lock.yml @@ -120,7 +120,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: update_release, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/repo-audit-analyzer.lock.yml b/.github/workflows/repo-audit-analyzer.lock.yml index 2470ffc05f..b2fa646020 100644 --- a/.github/workflows/repo-audit-analyzer.lock.yml +++ b/.github/workflows/repo-audit-analyzer.lock.yml @@ -118,7 +118,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/repo-tree-map.lock.yml b/.github/workflows/repo-tree-map.lock.yml index 060b6e0043..1c64bf7197 100644 --- a/.github/workflows/repo-tree-map.lock.yml +++ b/.github/workflows/repo-tree-map.lock.yml @@ -113,7 +113,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/repository-quality-improver.lock.yml b/.github/workflows/repository-quality-improver.lock.yml index 56fdf3c574..87da8ce96d 100644 --- a/.github/workflows/repository-quality-improver.lock.yml +++ b/.github/workflows/repository-quality-improver.lock.yml @@ -113,7 +113,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/research.lock.yml b/.github/workflows/research.lock.yml index 096efe011f..2930f19c51 100644 --- a/.github/workflows/research.lock.yml +++ b/.github/workflows/research.lock.yml @@ -117,7 +117,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/safe-output-health.lock.yml b/.github/workflows/safe-output-health.lock.yml index e4f4547c39..ddb8483917 100644 --- a/.github/workflows/safe-output-health.lock.yml +++ b/.github/workflows/safe-output-health.lock.yml @@ -115,7 +115,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/schema-consistency-checker.lock.yml b/.github/workflows/schema-consistency-checker.lock.yml index 2134eea16a..0b64762e1b 100644 --- a/.github/workflows/schema-consistency-checker.lock.yml +++ b/.github/workflows/schema-consistency-checker.lock.yml @@ -114,7 +114,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/scout.lock.yml b/.github/workflows/scout.lock.yml index da23f570f4..d34e3ad9ef 100644 --- a/.github/workflows/scout.lock.yml +++ b/.github/workflows/scout.lock.yml @@ -195,7 +195,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/security-compliance.lock.yml b/.github/workflows/security-compliance.lock.yml index 2fb5c9435b..f0da796855 100644 --- a/.github/workflows/security-compliance.lock.yml +++ b/.github/workflows/security-compliance.lock.yml @@ -134,7 +134,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/security-review.lock.yml b/.github/workflows/security-review.lock.yml index c67f60302a..13390c05b0 100644 --- a/.github/workflows/security-review.lock.yml +++ b/.github/workflows/security-review.lock.yml @@ -137,7 +137,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_pull_request_review_comment, submit_pull_request_review, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/semantic-function-refactor.lock.yml b/.github/workflows/semantic-function-refactor.lock.yml index e9f4ea31a4..0c06bd4f6a 100644 --- a/.github/workflows/semantic-function-refactor.lock.yml +++ b/.github/workflows/semantic-function-refactor.lock.yml @@ -113,7 +113,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, close_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/sergo.lock.yml b/.github/workflows/sergo.lock.yml index 755264df16..2271fc5284 100644 --- a/.github/workflows/sergo.lock.yml +++ b/.github/workflows/sergo.lock.yml @@ -114,7 +114,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/slide-deck-maintainer.lock.yml b/.github/workflows/slide-deck-maintainer.lock.yml index 116ebea9d7..721d318b4d 100644 --- a/.github/workflows/slide-deck-maintainer.lock.yml +++ b/.github/workflows/slide-deck-maintainer.lock.yml @@ -120,16 +120,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_pull_request, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/smoke-agent.lock.yml b/.github/workflows/smoke-agent.lock.yml index f845238f89..ef49687400 100644 --- a/.github/workflows/smoke-agent.lock.yml +++ b/.github/workflows/smoke-agent.lock.yml @@ -142,7 +142,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, assign_to_agent, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/smoke-claude.lock.yml b/.github/workflows/smoke-claude.lock.yml index 789a17a82c..95c1a9e3c0 100644 --- a/.github/workflows/smoke-claude.lock.yml +++ b/.github/workflows/smoke-claude.lock.yml @@ -162,14 +162,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, create_issue, close_pull_request, update_pull_request, create_pull_request_review_comment, submit_pull_request_review, resolve_pull_request_review_thread, add_labels, add_reviewer, push_to_pull_request_branch, missing_tool, missing_data - - **Pushing Changes to a Pull Request Branch** - - To push changes to the branch of a pull request: - 1. Make any file changes directly in the working directory. - 2. Add and commit your changes to the local copy of the pull request branch. Be careful to add exactly the files you intend, and verify you haven't deleted or changed any files you didn't intend to. - 3. Push the branch to the repo by using the push_to_pull_request_branch tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_push_to_pr_branch.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/smoke-codex.lock.yml b/.github/workflows/smoke-codex.lock.yml index 98c003d7ef..88d322a1ef 100644 --- a/.github/workflows/smoke-codex.lock.yml +++ b/.github/workflows/smoke-codex.lock.yml @@ -154,7 +154,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, create_issue, add_labels, remove_labels, unassign_from_user, hide_comment, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/smoke-copilot-arm.lock.yml b/.github/workflows/smoke-copilot-arm.lock.yml index 5671e18a69..5ac4e2fadd 100644 --- a/.github/workflows/smoke-copilot-arm.lock.yml +++ b/.github/workflows/smoke-copilot-arm.lock.yml @@ -154,7 +154,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, create_issue, create_discussion, create_pull_request_review_comment, submit_pull_request_review, add_labels, remove_labels, dispatch_workflow, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/smoke-copilot.lock.yml b/.github/workflows/smoke-copilot.lock.yml index 45390f2785..f65d4b342d 100644 --- a/.github/workflows/smoke-copilot.lock.yml +++ b/.github/workflows/smoke-copilot.lock.yml @@ -156,7 +156,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, create_issue, create_discussion, create_pull_request_review_comment, submit_pull_request_review, add_labels, remove_labels, dispatch_workflow, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/smoke-gemini.lock.yml b/.github/workflows/smoke-gemini.lock.yml index e9e19a9e84..a8e8042f25 100644 --- a/.github/workflows/smoke-gemini.lock.yml +++ b/.github/workflows/smoke-gemini.lock.yml @@ -153,7 +153,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, create_issue, add_labels, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/smoke-multi-pr.lock.yml b/.github/workflows/smoke-multi-pr.lock.yml index 8ad6fc6b3e..5e1e770c11 100644 --- a/.github/workflows/smoke-multi-pr.lock.yml +++ b/.github/workflows/smoke-multi-pr.lock.yml @@ -147,16 +147,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, create_pull_request, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/smoke-project.lock.yml b/.github/workflows/smoke-project.lock.yml index 0cfc643543..3b0b40b999 100644 --- a/.github/workflows/smoke-project.lock.yml +++ b/.github/workflows/smoke-project.lock.yml @@ -145,16 +145,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, create_issue, create_pull_request, add_labels, remove_labels, update_project, create_project_status_update, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/smoke-temporary-id.lock.yml b/.github/workflows/smoke-temporary-id.lock.yml index 3d0b461b3a..f3b81ea107 100644 --- a/.github/workflows/smoke-temporary-id.lock.yml +++ b/.github/workflows/smoke-temporary-id.lock.yml @@ -145,7 +145,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, create_issue, link_sub_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/smoke-test-tools.lock.yml b/.github/workflows/smoke-test-tools.lock.yml index fd2fde94aa..863eb7adda 100644 --- a/.github/workflows/smoke-test-tools.lock.yml +++ b/.github/workflows/smoke-test-tools.lock.yml @@ -144,7 +144,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/stale-repo-identifier.lock.yml b/.github/workflows/stale-repo-identifier.lock.yml index 9851b14257..3859476ced 100644 --- a/.github/workflows/stale-repo-identifier.lock.yml +++ b/.github/workflows/stale-repo-identifier.lock.yml @@ -127,7 +127,6 @@ jobs: Tools: create_issue, upload_asset, missing_tool, missing_data upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/static-analysis-report.lock.yml b/.github/workflows/static-analysis-report.lock.yml index 7d0f0e9f49..27b37b614c 100644 --- a/.github/workflows/static-analysis-report.lock.yml +++ b/.github/workflows/static-analysis-report.lock.yml @@ -114,7 +114,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/step-name-alignment.lock.yml b/.github/workflows/step-name-alignment.lock.yml index e2977a5df1..1f1e4bbd55 100644 --- a/.github/workflows/step-name-alignment.lock.yml +++ b/.github/workflows/step-name-alignment.lock.yml @@ -110,7 +110,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/sub-issue-closer.lock.yml b/.github/workflows/sub-issue-closer.lock.yml index 0ed3ce91da..dd50cf0f98 100644 --- a/.github/workflows/sub-issue-closer.lock.yml +++ b/.github/workflows/sub-issue-closer.lock.yml @@ -109,7 +109,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, update_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/super-linter.lock.yml b/.github/workflows/super-linter.lock.yml index 987bb90264..5009a8da9e 100644 --- a/.github/workflows/super-linter.lock.yml +++ b/.github/workflows/super-linter.lock.yml @@ -114,7 +114,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/technical-doc-writer.lock.yml b/.github/workflows/technical-doc-writer.lock.yml index ac6dfb8c10..72ad03e729 100644 --- a/.github/workflows/technical-doc-writer.lock.yml +++ b/.github/workflows/technical-doc-writer.lock.yml @@ -118,18 +118,11 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, create_pull_request, upload_asset, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat << 'GH_AW_PROMPT_EOF' upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/terminal-stylist.lock.yml b/.github/workflows/terminal-stylist.lock.yml index a1f548038c..0e2c34d38b 100644 --- a/.github/workflows/terminal-stylist.lock.yml +++ b/.github/workflows/terminal-stylist.lock.yml @@ -109,7 +109,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/test-create-pr-error-handling.lock.yml b/.github/workflows/test-create-pr-error-handling.lock.yml index f554ec0db5..d098197d06 100644 --- a/.github/workflows/test-create-pr-error-handling.lock.yml +++ b/.github/workflows/test-create-pr-error-handling.lock.yml @@ -107,16 +107,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_pull_request, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/test-dispatcher.lock.yml b/.github/workflows/test-dispatcher.lock.yml index 50e890facf..e75b9f4ce6 100644 --- a/.github/workflows/test-dispatcher.lock.yml +++ b/.github/workflows/test-dispatcher.lock.yml @@ -105,7 +105,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: dispatch_workflow, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/test-project-url-default.lock.yml b/.github/workflows/test-project-url-default.lock.yml index 5fa2d1d91c..48382e9871 100644 --- a/.github/workflows/test-project-url-default.lock.yml +++ b/.github/workflows/test-project-url-default.lock.yml @@ -105,7 +105,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: update_project, create_project_status_update, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/tidy.lock.yml b/.github/workflows/tidy.lock.yml index 22f765adac..29ad1a4ad4 100644 --- a/.github/workflows/tidy.lock.yml +++ b/.github/workflows/tidy.lock.yml @@ -143,23 +143,10 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_pull_request, push_to_pull_request_branch, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - - **Pushing Changes to a Pull Request Branch** - - To push changes to the branch of a pull request: - 1. Make any file changes directly in the working directory. - 2. Add and commit your changes to the local copy of the pull request branch. Be careful to add exactly the files you intend, and verify you haven't deleted or changed any files you didn't intend to. - 3. Push the branch to the repo by using the push_to_pull_request_branch tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat "/opt/gh-aw/prompts/safe_outputs_push_to_pr_branch.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/typist.lock.yml b/.github/workflows/typist.lock.yml index 8d5b5bcc51..c09e96aded 100644 --- a/.github/workflows/typist.lock.yml +++ b/.github/workflows/typist.lock.yml @@ -112,7 +112,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/ubuntu-image-analyzer.lock.yml b/.github/workflows/ubuntu-image-analyzer.lock.yml index 26785513e3..58e58b312f 100644 --- a/.github/workflows/ubuntu-image-analyzer.lock.yml +++ b/.github/workflows/ubuntu-image-analyzer.lock.yml @@ -112,16 +112,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_pull_request, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/unbloat-docs.lock.yml b/.github/workflows/unbloat-docs.lock.yml index 9c14e320ca..a86eb25434 100644 --- a/.github/workflows/unbloat-docs.lock.yml +++ b/.github/workflows/unbloat-docs.lock.yml @@ -140,18 +140,11 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, create_pull_request, upload_asset, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat << 'GH_AW_PROMPT_EOF' upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/video-analyzer.lock.yml b/.github/workflows/video-analyzer.lock.yml index bb4583e068..6aadf7cdbb 100644 --- a/.github/workflows/video-analyzer.lock.yml +++ b/.github/workflows/video-analyzer.lock.yml @@ -116,7 +116,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/weekly-editors-health-check.lock.yml b/.github/workflows/weekly-editors-health-check.lock.yml index 830d96973a..4ae90d2109 100644 --- a/.github/workflows/weekly-editors-health-check.lock.yml +++ b/.github/workflows/weekly-editors-health-check.lock.yml @@ -110,18 +110,11 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_pull_request, upload_asset, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat << 'GH_AW_PROMPT_EOF' upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/weekly-issue-summary.lock.yml b/.github/workflows/weekly-issue-summary.lock.yml index f312f5e647..1ecb23db61 100644 --- a/.github/workflows/weekly-issue-summary.lock.yml +++ b/.github/workflows/weekly-issue-summary.lock.yml @@ -109,7 +109,6 @@ jobs: Tools: create_discussion, upload_asset, missing_tool, missing_data upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/weekly-safe-outputs-spec-review.lock.yml b/.github/workflows/weekly-safe-outputs-spec-review.lock.yml index 2d91bde797..807b28f3d6 100644 --- a/.github/workflows/weekly-safe-outputs-spec-review.lock.yml +++ b/.github/workflows/weekly-safe-outputs-spec-review.lock.yml @@ -109,16 +109,9 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_pull_request, missing_tool, missing_data - - **Creating a Pull Request** - - To create a pull request: - 1. Make any file changes directly in the working directory. - 2. If you haven't done so already, create a local branch using an appropriate unique name. - 3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. - 4. Do not push your changes. That will be done by the tool. - 5. Create the pull request with the create_pull_request tool from safeoutputs. - + GH_AW_PROMPT_EOF + cat "/opt/gh-aw/prompts/safe_outputs_create_pull_request.md" + cat << 'GH_AW_PROMPT_EOF' The following GitHub context information is available for this workflow: diff --git a/.github/workflows/workflow-generator.lock.yml b/.github/workflows/workflow-generator.lock.yml index b87bdb1dbf..757d5fe15f 100644 --- a/.github/workflows/workflow-generator.lock.yml +++ b/.github/workflows/workflow-generator.lock.yml @@ -137,7 +137,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: update_issue, assign_to_agent, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/workflow-health-manager.lock.yml b/.github/workflows/workflow-health-manager.lock.yml index 5fea1cdabc..ed82edb73a 100644 --- a/.github/workflows/workflow-health-manager.lock.yml +++ b/.github/workflows/workflow-health-manager.lock.yml @@ -116,7 +116,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: add_comment, create_issue, update_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/workflow-normalizer.lock.yml b/.github/workflows/workflow-normalizer.lock.yml index 06c1329aed..16f4b3a9da 100644 --- a/.github/workflows/workflow-normalizer.lock.yml +++ b/.github/workflows/workflow-normalizer.lock.yml @@ -113,7 +113,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/.github/workflows/workflow-skill-extractor.lock.yml b/.github/workflows/workflow-skill-extractor.lock.yml index 2b7aa3593d..befbe3fd60 100644 --- a/.github/workflows/workflow-skill-extractor.lock.yml +++ b/.github/workflows/workflow-skill-extractor.lock.yml @@ -113,7 +113,6 @@ jobs: cat << 'GH_AW_PROMPT_EOF' Tools: create_issue, create_discussion, missing_tool, missing_data - The following GitHub context information is available for this workflow: diff --git a/actions/setup/md/safe_outputs_auto_create_issue.md b/actions/setup/md/safe_outputs_auto_create_issue.md new file mode 100644 index 0000000000..cd28d964e1 --- /dev/null +++ b/actions/setup/md/safe_outputs_auto_create_issue.md @@ -0,0 +1,2 @@ + +**IMPORTANT**: Report your findings or results by creating a GitHub issue using the create_issue tool. If you have no meaningful results to report, call the noop tool instead. diff --git a/actions/setup/md/safe_outputs_create_pull_request.md b/actions/setup/md/safe_outputs_create_pull_request.md new file mode 100644 index 0000000000..632c252ef5 --- /dev/null +++ b/actions/setup/md/safe_outputs_create_pull_request.md @@ -0,0 +1,9 @@ + +**Creating a Pull Request** + +To create a pull request: +1. Make any file changes directly in the working directory. +2. If you haven't done so already, create a local branch using an appropriate unique name. +3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to. +4. Do not push your changes. That will be done by the tool. +5. Create the pull request with the create_pull_request tool from safeoutputs. diff --git a/actions/setup/md/safe_outputs_push_to_pr_branch.md b/actions/setup/md/safe_outputs_push_to_pr_branch.md new file mode 100644 index 0000000000..087b89203e --- /dev/null +++ b/actions/setup/md/safe_outputs_push_to_pr_branch.md @@ -0,0 +1,7 @@ + +**Pushing Changes to a Pull Request Branch** + +To push changes to the branch of a pull request: +1. Make any file changes directly in the working directory. +2. Add and commit your changes to the local copy of the pull request branch. Be careful to add exactly the files you intend, and verify you haven't deleted or changed any files you didn't intend to. +3. Push the branch to the repo by using the push_to_pull_request_branch tool from safeoutputs. diff --git a/pkg/workflow/safe_outputs_default_create_issue_test.go b/pkg/workflow/safe_outputs_default_create_issue_test.go index c77a1b2e6f..b2c9ddf11b 100644 --- a/pkg/workflow/safe_outputs_default_create_issue_test.go +++ b/pkg/workflow/safe_outputs_default_create_issue_test.go @@ -261,7 +261,7 @@ func TestAutoInjectedCreateIssuePrompt(t *testing.T) { tests := []struct { name string safeOutputs *SafeOutputsConfig - expectSpecific bool // expect the "IMPORTANT: Report your findings" instruction + expectSpecific bool // expect the auto_create_issue file reference }{ { name: "auto-injected create-issue produces specific prompt", @@ -296,19 +296,21 @@ func TestAutoInjectedCreateIssuePrompt(t *testing.T) { for _, tt := range tests { t.Run(tt.name, func(t *testing.T) { - var b strings.Builder - generateSafeOutputsPerToolInstructions(&b, tt.safeOutputs) - output := b.String() + compiler := &Compiler{} + var yaml strings.Builder + data := &WorkflowData{ + ParsedTools: NewTools(map[string]any{}), + SafeOutputs: tt.safeOutputs, + } + compiler.generateUnifiedPromptStep(&yaml, data) + output := yaml.String() - specificInstruction := "**IMPORTANT**: Report your findings or results by creating a GitHub issue" if tt.expectSpecific { - assert.Contains(t, output, specificInstruction, - "Auto-injected create-issue should include specific prompt instruction") - assert.Contains(t, output, "noop tool instead", - "Auto-injected create-issue prompt should mention calling noop as alternative") + assert.Contains(t, output, safeOutputsAutoCreateIssueFile, + "Auto-injected create-issue should include the auto_create_issue file reference") } else { - assert.NotContains(t, output, specificInstruction, - "Non-auto-injected create-issue should not include specific auto-inject instruction") + assert.NotContains(t, output, safeOutputsAutoCreateIssueFile, + "Non-auto-injected create-issue should not include the auto_create_issue file reference") } }) } diff --git a/pkg/workflow/sh.go b/pkg/workflow/sh.go index 82f22a4058..b79dd0ce7b 100644 --- a/pkg/workflow/sh.go +++ b/pkg/workflow/sh.go @@ -12,17 +12,20 @@ var shLog = logger.New("workflow:sh") // Prompt file paths at runtime (copied by setup action) const ( - promptsDir = "/opt/gh-aw/prompts" - prContextPromptFile = "pr_context_prompt.md" - tempFolderPromptFile = "temp_folder_prompt.md" - playwrightPromptFile = "playwright_prompt.md" - markdownPromptFile = "markdown.md" - xpiaPromptFile = "xpia.md" - cacheMemoryPromptFile = "cache_memory_prompt.md" - cacheMemoryPromptMultiFile = "cache_memory_prompt_multi.md" - repoMemoryPromptFile = "repo_memory_prompt.md" - repoMemoryPromptMultiFile = "repo_memory_prompt_multi.md" - safeOutputsPromptFile = "safe_outputs_prompt.md" + promptsDir = "/opt/gh-aw/prompts" + prContextPromptFile = "pr_context_prompt.md" + tempFolderPromptFile = "temp_folder_prompt.md" + playwrightPromptFile = "playwright_prompt.md" + markdownPromptFile = "markdown.md" + xpiaPromptFile = "xpia.md" + cacheMemoryPromptFile = "cache_memory_prompt.md" + cacheMemoryPromptMultiFile = "cache_memory_prompt_multi.md" + repoMemoryPromptFile = "repo_memory_prompt.md" + repoMemoryPromptMultiFile = "repo_memory_prompt_multi.md" + safeOutputsPromptFile = "safe_outputs_prompt.md" + safeOutputsCreatePRFile = "safe_outputs_create_pull_request.md" + safeOutputsPushToBranchFile = "safe_outputs_push_to_pr_branch.md" + safeOutputsAutoCreateIssueFile = "safe_outputs_auto_create_issue.md" ) // GitHub context prompt is kept embedded because it contains GitHub Actions expressions diff --git a/pkg/workflow/unified_prompt_step.go b/pkg/workflow/unified_prompt_step.go index a9e33f8beb..eeba2334c2 100644 --- a/pkg/workflow/unified_prompt_step.go +++ b/pkg/workflow/unified_prompt_step.go @@ -291,17 +291,9 @@ func (c *Compiler) collectPromptSections(data *WorkflowData) []PromptSection { Content: safeOutputsPromptFile, IsFile: true, }) - // Per-tool instructions (dynamic, depends on which tools are enabled) - var perToolBuilder strings.Builder - perToolBuilder.WriteString("\n") - generateSafeOutputsPerToolInstructions(&perToolBuilder, data.SafeOutputs) - perToolBuilder.WriteString("") - sections = append(sections, PromptSection{ - Content: perToolBuilder.String(), - IsFile: false, - }) + // Per-tool sections: opening tag + tools list (inline), tool instruction files, closing tag + sections = append(sections, buildSafeOutputsSections(data.SafeOutputs)...) } - // 8. GitHub context (if GitHub tool is enabled) if hasGitHubTool(data.ParsedTools) { unifiedPromptLog.Print("Adding GitHub context section") @@ -587,18 +579,21 @@ func (c *Compiler) generateUnifiedPromptCreationStep(yaml *strings.Builder, buil var safeOutputsPromptLog = logger.New("workflow:safe_outputs_prompt") -// generateSafeOutputsPerToolInstructions appends per-tool usage instructions for each -// configured safe-output capability. It is called from collectPromptSections to inject -// tool-specific guidance inside the XML block. +// buildSafeOutputsSections returns the PromptSections that form the block. +// The block contains: +// 1. An inline opening tag with a compact Tools list (dynamic, depends on which tools are enabled). +// 2. File references for tools that require multi-step instructions (create_pull_request, +// push_to_pull_request_branch, auto-injected create_issue notice). +// 3. An inline closing tag. // // The static intro (gh CLI warning, temporary ID rules, noop note) lives in -// actions/setup/md/safe_outputs_prompt.md and is included separately via a file reference. -func generateSafeOutputsPerToolInstructions(b *strings.Builder, safeOutputs *SafeOutputsConfig) { +// actions/setup/md/safe_outputs_prompt.md and is included by the caller before these sections. +func buildSafeOutputsSections(safeOutputs *SafeOutputsConfig) []PromptSection { if safeOutputs == nil { - return + return nil } - safeOutputsPromptLog.Print("Generating safe outputs per-tool instructions") + safeOutputsPromptLog.Print("Building safe outputs sections") // Build compact list of enabled tool names var tools []string @@ -712,38 +707,42 @@ func generateSafeOutputsPerToolInstructions(b *strings.Builder, safeOutputs *Saf } if len(tools) == 0 { - return + return nil } - fmt.Fprintf(b, "Tools: %s\n\n", strings.Join(tools, ", ")) + var sections []PromptSection - // Special multi-step instructions for complex tools + // Inline opening: XML tag + compact tools list + sections = append(sections, PromptSection{ + Content: "\nTools: " + strings.Join(tools, ", "), + IsFile: false, + }) + + // File sections for tools with multi-step instructions if safeOutputs.CreatePullRequests != nil { - b.WriteString("**Creating a Pull Request**\n\n") - b.WriteString("To create a pull request:\n") - b.WriteString("1. Make any file changes directly in the working directory.\n") - b.WriteString("2. If you haven't done so already, create a local branch using an appropriate unique name.\n") - b.WriteString("3. Add and commit your changes to the branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Verify you haven't deleted or changed any files you didn't intend to.\n") - b.WriteString("4. Do not push your changes. That will be done by the tool.\n") - fmt.Fprintf(b, "5. Create the pull request with the create_pull_request tool from %s.\n\n", constants.SafeOutputsMCPServerID) + sections = append(sections, PromptSection{Content: safeOutputsCreatePRFile, IsFile: true}) } - if safeOutputs.PushToPullRequestBranch != nil { - b.WriteString("**Pushing Changes to a Pull Request Branch**\n\n") - b.WriteString("To push changes to the branch of a pull request:\n") - b.WriteString("1. Make any file changes directly in the working directory.\n") - b.WriteString("2. Add and commit your changes to the local copy of the pull request branch. Be careful to add exactly the files you intend, and verify you haven't deleted or changed any files you didn't intend to.\n") - fmt.Fprintf(b, "3. Push the branch to the repo by using the push_to_pull_request_branch tool from %s.\n\n", constants.SafeOutputsMCPServerID) + sections = append(sections, PromptSection{Content: safeOutputsPushToBranchFile, IsFile: true}) } - if safeOutputs.UploadAssets != nil { - fmt.Fprintf(b, "upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (%s).\n\n", constants.SafeOutputsMCPServerID) + sections = append(sections, PromptSection{ + Content: "\nupload_asset: provide a file path; returns a URL; assets are published after the workflow completes (" + constants.SafeOutputsMCPServerID + ").", + IsFile: false, + }) } - // Auto-injected create_issue special notice if safeOutputs.CreateIssues != nil && safeOutputs.AutoInjectedCreateIssue { - b.WriteString("**IMPORTANT**: Report your findings or results by creating a GitHub issue using the create_issue tool. If you have no meaningful results to report, call the noop tool instead.\n\n") + sections = append(sections, PromptSection{Content: safeOutputsAutoCreateIssueFile, IsFile: true}) } + + // Inline closing tag + sections = append(sections, PromptSection{ + Content: "", + IsFile: false, + }) + + return sections } var promptStepHelperLog = logger.New("workflow:prompt_step_helper") From 7982eb2bd4873c1ded9c013b959c06d87d1ae67b Mon Sep 17 00:00:00 2001 From: Codex Date: Sun, 22 Feb 2026 20:42:39 +0000 Subject: [PATCH 6/7] Add changeset [skip-ci] --- .changeset/patch-refactor-safe-outputs-prompt.md | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 .changeset/patch-refactor-safe-outputs-prompt.md diff --git a/.changeset/patch-refactor-safe-outputs-prompt.md b/.changeset/patch-refactor-safe-outputs-prompt.md new file mode 100644 index 0000000000..5a6d3e8bdc --- /dev/null +++ b/.changeset/patch-refactor-safe-outputs-prompt.md @@ -0,0 +1,4 @@ +--- +"gh-aw": patch +--- +Refactor the safe outputs prompt to source the intro and per-tool guidance from markdown templates so it is easier to maintain and uses fewer tokens. From 28151b326f6c76493cea96bc7cae54e2aedd4aeb Mon Sep 17 00:00:00 2001 From: Smoke Test Date: Sun, 22 Feb 2026 20:47:45 +0000 Subject: [PATCH 7/7] test: Add smoke test file for run 22284918558 --- smoke-test-push-22284918558.md | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 smoke-test-push-22284918558.md diff --git a/smoke-test-push-22284918558.md b/smoke-test-push-22284918558.md new file mode 100644 index 0000000000..6761e8cd39 --- /dev/null +++ b/smoke-test-push-22284918558.md @@ -0,0 +1,3 @@ +# Smoke Test Push + +Test file for PR push - smoke test run 22284918558