From 21f117c27efa01ae5ce6dc8a1d3c6f19d0e2738c Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Tue, 24 Feb 2026 03:53:50 +0000 Subject: [PATCH 1/2] Initial plan From 234b514a3bcfa3f8caafd094635134888a38b0ac Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Tue, 24 Feb 2026 04:18:53 +0000 Subject: [PATCH 2/2] Strengthen noop documentation and add explicit noop instructions to all workflow prompts Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- .../workflows/agent-performance-analyzer.md | 6 +++++ .github/workflows/agent-persona-explorer.md | 6 +++++ .github/workflows/ai-moderator.md | 8 ++++++- .github/workflows/archie.md | 8 ++++++- .github/workflows/artifacts-summary.md | 8 ++++++- .github/workflows/audit-workflows.md | 6 +++++ .github/workflows/auto-triage-issues.md | 6 +++++ .github/workflows/blog-auditor.md | 8 ++++++- .github/workflows/bot-detection.md | 6 +++++ .github/workflows/brave.md | 6 +++++ .github/workflows/ci-coach.md | 6 +++++ .../workflows/claude-code-user-docs-review.md | 6 +++++ .github/workflows/cli-consistency-checker.md | 6 +++++ .github/workflows/cli-version-checker.md | 6 +++++ .github/workflows/cloclo.md | 6 +++++ .github/workflows/code-scanning-fixer.md | 8 ++++++- .github/workflows/code-simplifier.md | 6 +++++ .github/workflows/commit-changes-analyzer.md | 6 +++++ .github/workflows/contribution-check.md | 8 ++++++- .github/workflows/copilot-agent-analysis.md | 6 +++++ .../workflows/copilot-cli-deep-research.md | 6 +++++ .github/workflows/copilot-pr-merged-report.md | 6 +++++ .github/workflows/copilot-pr-nlp-analysis.md | 8 ++++++- .../workflows/copilot-pr-prompt-analysis.md | 8 ++++++- .github/workflows/copilot-session-insights.md | 8 ++++++- .github/workflows/craft.md | 6 +++++ .../workflows/daily-assign-issue-to-user.md | 6 +++++ .github/workflows/daily-choice-test.md | 6 +++++ .github/workflows/daily-cli-performance.md | 8 ++++++- .github/workflows/daily-code-metrics.md | 8 ++++++- .github/workflows/daily-compiler-quality.md | 6 +++++ .../workflows/daily-copilot-token-report.md | 8 ++++++- .github/workflows/daily-doc-updater.md | 6 +++++ .github/workflows/daily-fact.md | 8 ++++++- .github/workflows/daily-file-diet.md | 6 +++++ .github/workflows/daily-firewall-report.md | 6 +++++ .github/workflows/daily-issues-report.md | 8 ++++++- .github/workflows/daily-news.md | 8 ++++++- .../workflows/daily-observability-report.md | 6 +++++ .../workflows/daily-performance-summary.md | 6 +++++ .github/workflows/daily-regulatory.md | 6 +++++ .../daily-rendering-scripts-verifier.md | 6 +++++ .github/workflows/daily-repo-chronicle.md | 8 ++++++- .../workflows/daily-safe-output-optimizer.md | 6 +++++ .github/workflows/daily-secrets-analysis.md | 8 ++++++- .github/workflows/daily-semgrep-scan.md | 6 +++++ .../workflows/daily-syntax-error-quality.md | 6 +++++ .../daily-team-evolution-insights.md | 6 +++++ .github/workflows/daily-team-status.md | 6 +++++ .../daily-testify-uber-super-expert.md | 6 +++++ .github/workflows/daily-workflow-updater.md | 6 +++++ .github/workflows/deep-report.md | 6 +++++ .github/workflows/delight.md | 6 +++++ .github/workflows/dependabot-burner.md | 6 +++++ .github/workflows/dependabot-go-checker.md | 6 +++++ .github/workflows/dev-hawk.md | 6 +++++ .github/workflows/dev.md | 6 +++++ .../workflows/developer-docs-consolidator.md | 6 +++++ .github/workflows/dictation-prompt.md | 6 +++++ .github/workflows/discussion-task-miner.md | 6 +++++ .github/workflows/docs-noob-tester.md | 8 ++++++- .github/workflows/draft-pr-cleanup.md | 6 +++++ .../workflows/example-workflow-analyzer.md | 8 ++++++- .github/workflows/firewall-escape.md | 8 ++++++- .github/workflows/functional-pragmatist.md | 6 +++++ .../github-mcp-structural-analysis.md | 6 +++++ .github/workflows/github-mcp-tools-report.md | 8 ++++++- .../workflows/github-remote-mcp-auth-test.md | 6 +++++ .github/workflows/glossary-maintainer.md | 6 +++++ .github/workflows/go-fan.md | 6 +++++ .github/workflows/go-logger.md | 6 +++++ .github/workflows/go-pattern-detector.md | 6 +++++ .github/workflows/gpclean.md | 6 +++++ .github/workflows/grumpy-reviewer.md | 6 +++++ .github/workflows/instructions-janitor.md | 6 +++++ .github/workflows/issue-arborist.md | 6 +++++ .github/workflows/issue-triage-agent.md | 8 ++++++- .github/workflows/jsweep.md | 6 +++++ .github/workflows/layout-spec-maintainer.md | 6 +++++ .github/workflows/lockfile-stats.md | 8 ++++++- .github/workflows/mcp-inspector.md | 8 ++++++- .github/workflows/mergefest.md | 6 +++++ .github/workflows/org-health-report.md | 8 ++++++- .github/workflows/pdf-summary.md | 6 +++++ .github/workflows/plan.md | 6 +++++ .github/workflows/poem-bot.md | 8 ++++++- .github/workflows/portfolio-analyst.md | 6 +++++ .github/workflows/pr-nitpick-reviewer.md | 6 +++++ .github/workflows/pr-triage-agent.md | 6 +++++ .../workflows/prompt-clustering-analysis.md | 6 +++++ .github/workflows/python-data-charts.md | 8 ++++++- .github/workflows/q.md | 8 ++++++- .github/workflows/refiner.md | 6 +++++ .github/workflows/release.md | 6 +++++ .github/workflows/repo-audit-analyzer.md | 6 +++++ .github/workflows/repo-tree-map.md | 8 ++++++- .../workflows/repository-quality-improver.md | 6 +++++ .github/workflows/research.md | 8 ++++++- .github/workflows/safe-output-health.md | 6 +++++ .../workflows/schema-consistency-checker.md | 6 +++++ .github/workflows/scout.md | 6 +++++ .github/workflows/security-compliance.md | 6 +++++ .github/workflows/security-review.md | 6 +++++ .../workflows/semantic-function-refactor.md | 6 +++++ .github/workflows/sergo.md | 6 +++++ .github/workflows/smoke-claude.lock.yml | 8 ++++++- .github/workflows/smoke-claude.md | 6 +++++ .github/workflows/smoke-codex.md | 6 +++++ .github/workflows/smoke-copilot-arm.md | 6 +++++ .github/workflows/smoke-copilot.md | 6 +++++ .github/workflows/smoke-gemini.md | 6 +++++ .github/workflows/smoke-multi-pr.md | 6 +++++ .github/workflows/smoke-project.md | 6 +++++ .github/workflows/smoke-temporary-id.md | 6 +++++ .github/workflows/smoke-test-tools.md | 6 +++++ .github/workflows/stale-repo-identifier.md | 8 ++++++- .github/workflows/static-analysis-report.md | 6 +++++ .github/workflows/step-name-alignment.md | 6 +++++ .github/workflows/sub-issue-closer.md | 6 +++++ .github/workflows/super-linter.md | 6 +++++ .github/workflows/technical-doc-writer.md | 8 ++++++- .github/workflows/terminal-stylist.md | 6 +++++ .../test-create-pr-error-handling.md | 6 +++++ .github/workflows/test-dispatcher.md | 6 +++++ .github/workflows/test-project-url-default.md | 6 +++++ .github/workflows/tidy.md | 8 ++++++- .github/workflows/typist.md | 6 +++++ .github/workflows/ubuntu-image-analyzer.md | 6 +++++ .github/workflows/unbloat-docs.md | 8 ++++++- .github/workflows/video-analyzer.md | 8 ++++++- .../workflows/weekly-editors-health-check.md | 6 +++++ .github/workflows/weekly-issue-summary.md | 8 ++++++- .../weekly-safe-outputs-spec-review.md | 6 +++++ .github/workflows/workflow-generator.md | 6 +++++ .github/workflows/workflow-health-manager.md | 6 +++++ .github/workflows/workflow-normalizer.md | 6 +++++ .github/workflows/workflow-skill-extractor.md | 6 +++++ actions/setup/md/safe_outputs_prompt.md | 10 +++++++- .../content/docs/reference/safe-outputs.md | 23 ++++++++++++++++++- 139 files changed, 890 insertions(+), 39 deletions(-) diff --git a/.github/workflows/agent-performance-analyzer.md b/.github/workflows/agent-performance-analyzer.md index 673cb60f965..c6c720fcbcb 100644 --- a/.github/workflows/agent-performance-analyzer.md +++ b/.github/workflows/agent-performance-analyzer.md @@ -634,3 +634,9 @@ Your effectiveness is measured by: - Agent ecosystem health and sustainability Execute all phases systematically and maintain an objective, data-driven approach to agent performance analysis. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/agent-persona-explorer.md b/.github/workflows/agent-persona-explorer.md index 74341b0dd06..09ff1b3eafd 100644 --- a/.github/workflows/agent-persona-explorer.md +++ b/.github/workflows/agent-persona-explorer.md @@ -227,3 +227,9 @@ Your effectiveness is measured by: - **Consistency**: Maintain objective, research-focused methodology Execute all phases systematically and maintain an objective, research-focused approach to understanding the agentic-workflows custom agent's capabilities and limitations. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/ai-moderator.md b/.github/workflows/ai-moderator.md index e8ef6b2d362..25b7700e30e 100644 --- a/.github/workflows/ai-moderator.md +++ b/.github/workflows/ai-moderator.md @@ -132,4 +132,10 @@ Based on your analysis: - Technical discussions may naturally contain links to resources, documentation, or related issues - New contributors may have less polished writing - this doesn't necessarily indicate AI generation - Provide clear reasoning for each detection in your analysis -- Only take action if you have high confidence in the detection \ No newline at end of file +- Only take action if you have high confidence in the detection + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/archie.md b/.github/workflows/archie.md index cbd7f3d762a..c3ede9839ba 100644 --- a/.github/workflows/archie.md +++ b/.github/workflows/archie.md @@ -214,4 +214,10 @@ A successful Archie run: ## Begin Your Analysis -Examine the current context, analyze any linked references, generate your Mermaid diagrams using Serena, validate them, and post your visualization comment! \ No newline at end of file +Examine the current context, analyze any linked references, generate your Mermaid diagrams using Serena, validate them, and post your visualization comment! + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/artifacts-summary.md b/.github/workflows/artifacts-summary.md index 4a6a4670df0..5a7f6859273 100644 --- a/.github/workflows/artifacts-summary.md +++ b/.github/workflows/artifacts-summary.md @@ -86,4 +86,10 @@ Create an issue with a markdown table like this: - Focus on workflows that actually generate artifacts (skip those without any) - Convert sizes to human-readable formats (MB, GB) - Consider artifact retention policies in your analysis -- Include both successful and failed runs in the analysis, ignore cancelled runs \ No newline at end of file +- Include both successful and failed runs in the analysis, ignore cancelled runs + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/audit-workflows.md b/.github/workflows/audit-workflows.md index 5e9d9e37a61..923282ceee7 100644 --- a/.github/workflows/audit-workflows.md +++ b/.github/workflows/audit-workflows.md @@ -172,3 +172,9 @@ Output is saved to: /tmp/gh-aw/aw-mcp/logs Memory structure: `/tmp/gh-aw/repo-memory/default/{audits,patterns,metrics}/*.json` Always create discussion with findings and update repo memory. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/auto-triage-issues.md b/.github/workflows/auto-triage-issues.md index 68b06e00ae4..087e529b893 100644 --- a/.github/workflows/auto-triage-issues.md +++ b/.github/workflows/auto-triage-issues.md @@ -314,3 +314,9 @@ When running on schedule, create a discussion report following the formatting gu - Median time to first label: <5 minutes for new issues - Label accuracy: ≥90% (minimal maintainer corrections needed) - False positive rate: <10% + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/blog-auditor.md b/.github/workflows/blog-auditor.md index 8654e50900b..c893e277003 100644 --- a/.github/workflows/blog-auditor.md +++ b/.github/workflows/blog-auditor.md @@ -298,4 +298,10 @@ A successful audit: - ✅ Provides actionable information for remediation - ✅ Completes within timeout limits -Begin your audit now. Navigate to the blog using Playwright, capture the accessibility snapshot, extract and validate code snippets, validate all criteria, and report your findings. \ No newline at end of file +Begin your audit now. Navigate to the blog using Playwright, capture the accessibility snapshot, extract and validate code snippets, validate all criteria, and report your findings. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/bot-detection.md b/.github/workflows/bot-detection.md index a9fe823d6e4..9a81ac0aaf6 100644 --- a/.github/workflows/bot-detection.md +++ b/.github/workflows/bot-detection.md @@ -917,3 +917,9 @@ Map score → severity: - `None`: `0` (do not include) If you cannot verify a signal from available data, score it as `0` and do not infer. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/brave.md b/.github/workflows/brave.md index 1ac89a794b0..87bfb674c41 100644 --- a/.github/workflows/brave.md +++ b/.github/workflows/brave.md @@ -125,3 +125,9 @@ Your search summary should be formatted as a comment with: - **Attribution**: Always cite your sources with proper links Remember: Your goal is to provide valuable, actionable information from web searches that helps resolve the issue or improve the pull request. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/ci-coach.md b/.github/workflows/ci-coach.md index 771b1eb75ac..24a856f2c88 100644 --- a/.github/workflows/ci-coach.md +++ b/.github/workflows/ci-coach.md @@ -393,3 +393,9 @@ The CI Coach workflow must NEVER alter test code (`*_test.go` files) in ways tha ✅ Completed analysis in under 30 minutes Begin your analysis now. Study the CI configuration, analyze the run data, and identify concrete opportunities to make the test suite more efficient while minimizing costs. If you propose changes to the CI workflow, validate them by running the build, lint, and test commands before creating a pull request. Only create a PR if all validations pass. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/claude-code-user-docs-review.md b/.github/workflows/claude-code-user-docs-review.md index 91a2efb8568..8c7138f5646 100644 --- a/.github/workflows/claude-code-user-docs-review.md +++ b/.github/workflows/claude-code-user-docs-review.md @@ -537,3 +537,9 @@ Your report is successful if it: - This is a daily workflow - findings should be stored in cache-memory for tracking trends over time Execute your review systematically and provide a comprehensive report that helps make gh-aw accessible to all AI tool users, not just Copilot users. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/cli-consistency-checker.md b/.github/workflows/cli-consistency-checker.md index 6659d16ee09..5dd183f78c2 100644 --- a/.github/workflows/cli-consistency-checker.md +++ b/.github/workflows/cli-consistency-checker.md @@ -248,3 +248,9 @@ All CLI output comes from the repository's own codebase, so treat it as trusted - Compare CLI output with documentation - Create issues for any inconsistencies found - Be specific with exact quotes from CLI output in your issue reports + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/cli-version-checker.md b/.github/workflows/cli-version-checker.md index 38fd48036d9..689f1981cd2 100644 --- a/.github/workflows/cli-version-checker.md +++ b/.github/workflows/cli-version-checker.md @@ -398,3 +398,9 @@ npm view @github/copilot --json 2>/dev/null | jq -r '.version' - Skip PR creation if recompile fails - Exit successfully if no updates found - Document incomplete research if rate-limited + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/cloclo.md b/.github/workflows/cloclo.md index 6dd96d890e0..540ccb1df51 100644 --- a/.github/workflows/cloclo.md +++ b/.github/workflows/cloclo.md @@ -193,3 +193,9 @@ Now analyze the content above and execute the appropriate action. Remember: - ✅ Add 👍 reaction after posting comments - ❌ Never modify `.github/.workflows` directory - ❌ Don't make changes without understanding the request + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/code-scanning-fixer.md b/.github/workflows/code-scanning-fixer.md index 660925eaf72..8558bb8ab1d 100644 --- a/.github/workflows/code-scanning-fixer.md +++ b/.github/workflows/code-scanning-fixer.md @@ -217,4 +217,10 @@ If any step fails: - **Never Execute Untrusted Code**: Use read-only analysis tools - **Track Progress**: Cache ensures no duplicate work -Remember: Your goal is to provide a secure, well-tested fix that can be reviewed and merged safely. Focus on quality and correctness over speed. \ No newline at end of file +Remember: Your goal is to provide a secure, well-tested fix that can be reviewed and merged safely. Focus on quality and correctness over speed. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/code-simplifier.md b/.github/workflows/code-simplifier.md index 8208c82c3a8..87b119da11f 100644 --- a/.github/workflows/code-simplifier.md +++ b/.github/workflows/code-simplifier.md @@ -394,3 +394,9 @@ Your output MUST either: 3. **If simplifications made**: Create a PR with the changes using safe-outputs Begin your code simplification analysis now. Find recently modified code, assess simplification opportunities, apply improvements while preserving functionality, validate changes, and create a PR if beneficial. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/commit-changes-analyzer.md b/.github/workflows/commit-changes-analyzer.md index 00c9a4345ab..e6e32a5b0d7 100644 --- a/.github/workflows/commit-changes-analyzer.md +++ b/.github/workflows/commit-changes-analyzer.md @@ -308,3 +308,9 @@ If any of these conditions occur, explain clearly in the discussion: - No commits found in the range (commit is already at HEAD) Make the error message helpful so the user knows how to correct the input. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/contribution-check.md b/.github/workflows/contribution-check.md index 8bf9e2e17d1..bb821a09563 100644 --- a/.github/workflows/contribution-check.md +++ b/.github/workflows/contribution-check.md @@ -178,4 +178,10 @@ If any subagent call failed (❓), also apply `outdated`. - **Write to `${{ github.repository }}`** — reports go here as issues. - **Use safe output tools for target repository interactions** — use `add-comment` and `add-labels` safe output tools to post comments and labels to PRs in the target repository `${{ env.TARGET_REPOSITORY }}`. Never use `gh` CLI or direct API calls for writes. - Close the previous report issue when creating a new one (`close-older-issues: true`). -- Be constructive in assessments — these reports help maintainers prioritize, not gatekeep. \ No newline at end of file +- Be constructive in assessments — these reports help maintainers prioritize, not gatekeep. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/copilot-agent-analysis.md b/.github/workflows/copilot-agent-analysis.md index e1b50dc9b3e..da246d7d70f 100644 --- a/.github/workflows/copilot-agent-analysis.md +++ b/.github/workflows/copilot-agent-analysis.md @@ -479,3 +479,9 @@ A successful **concise** analysis: - ✅ Provides 1-2 actionable insights maximum **Remember**: Less is more. Focus on key metrics and notable changes only. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/copilot-cli-deep-research.md b/.github/workflows/copilot-cli-deep-research.md index 49eb53d6c00..46caa67fb05 100644 --- a/.github/workflows/copilot-cli-deep-research.md +++ b/.github/workflows/copilot-cli-deep-research.md @@ -507,3 +507,9 @@ A successful research report should: - ✅ Consider security, performance, and developer experience **Remember**: The goal is to help the team make better use of Copilot CLI's capabilities and improve the overall quality of agentic workflows in this repository. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/copilot-pr-merged-report.md b/.github/workflows/copilot-pr-merged-report.md index a3426512435..94065fb1230 100644 --- a/.github/workflows/copilot-pr-merged-report.md +++ b/.github/workflows/copilot-pr-merged-report.md @@ -310,3 +310,9 @@ A successful report: - ✅ Completes within 10-minute timeout Begin your analysis now. Use the `gh` safe-input tool for all GitHub CLI operations. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/copilot-pr-nlp-analysis.md b/.github/workflows/copilot-pr-nlp-analysis.md index 7a02d6c8051..63df99a6b84 100644 --- a/.github/workflows/copilot-pr-nlp-analysis.md +++ b/.github/workflows/copilot-pr-nlp-analysis.md @@ -540,4 +540,10 @@ Store reusable components and historical data: --- -**Remember**: Focus on identifying actionable patterns in Copilot PR conversations that can inform prompt improvements, development practices, and collaboration quality. \ No newline at end of file +**Remember**: Focus on identifying actionable patterns in Copilot PR conversations that can inform prompt improvements, development practices, and collaboration quality. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/copilot-pr-prompt-analysis.md b/.github/workflows/copilot-pr-prompt-analysis.md index 6455c1cdb6a..94b0ea1c8ff 100644 --- a/.github/workflows/copilot-pr-prompt-analysis.md +++ b/.github/workflows/copilot-pr-prompt-analysis.md @@ -351,4 +351,10 @@ A successful analysis: - ✅ Creates discussion with clear insights - ✅ Includes concrete examples of good and poor prompts -**Remember**: The goal is to help developers write better prompts that lead to more successful PR merges. \ No newline at end of file +**Remember**: The goal is to help developers write better prompts that lead to more successful PR merges. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/copilot-session-insights.md b/.github/workflows/copilot-session-insights.md index 6edd4816ca4..86ce7facb4f 100644 --- a/.github/workflows/copilot-session-insights.md +++ b/.github/workflows/copilot-session-insights.md @@ -512,4 +512,10 @@ A successful analysis includes: --- -Begin your analysis by verifying the downloaded session data, loading historical context from cache memory, and proceeding through the analysis phases systematically. \ No newline at end of file +Begin your analysis by verifying the downloaded session data, loading historical context from cache memory, and proceeding through the analysis phases systematically. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/craft.md b/.github/workflows/craft.md index 07616c3d47e..9b990b6b5c6 100644 --- a/.github/workflows/craft.md +++ b/.github/workflows/craft.md @@ -280,3 +280,9 @@ Now analyze the user's request: "${{ steps.sanitized.outputs.text }}" 4. Compile and validate 5. Push changes using `push-to-pull-request-branch` 6. Report success with details + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/daily-assign-issue-to-user.md b/.github/workflows/daily-assign-issue-to-user.md index f163b0123c2..b329a79ea81 100644 --- a/.github/workflows/daily-assign-issue-to-user.md +++ b/.github/workflows/daily-assign-issue-to-user.md @@ -39,3 +39,9 @@ If you find a match: 2. Use `add-comment` with a short explanation (1-2 sentences) If no unassigned issue exists, exit successfully without taking action. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/daily-choice-test.md b/.github/workflows/daily-choice-test.md index afbb890c962..fe7cafee025 100644 --- a/.github/workflows/daily-choice-test.md +++ b/.github/workflows/daily-choice-test.md @@ -73,3 +73,9 @@ Make your selection based on the day of the week: - Tuesday/Thursday: Use "production" environment with "integration" tests Provide a brief explanation of why you chose this configuration. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/daily-cli-performance.md b/.github/workflows/daily-cli-performance.md index 4dd089463c3..b7789a3885a 100644 --- a/.github/workflows/daily-cli-performance.md +++ b/.github/workflows/daily-cli-performance.md @@ -687,4 +687,10 @@ Each entry contains: } ``` -Begin your daily performance analysis now! \ No newline at end of file +Begin your daily performance analysis now! + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/daily-code-metrics.md b/.github/workflows/daily-code-metrics.md index 2a893722d33..1af69721b1f 100644 --- a/.github/workflows/daily-code-metrics.md +++ b/.github/workflows/daily-code-metrics.md @@ -455,4 +455,10 @@ This ensures the quality score reflects actionable source code volatility, not n - Generate all 6 required visualization charts - Upload charts as assets for permanent URLs - Embed charts in discussion report with analysis -- Store metrics to repo memory, create discussion report with visualizations \ No newline at end of file +- Store metrics to repo memory, create discussion report with visualizations + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/daily-compiler-quality.md b/.github/workflows/daily-compiler-quality.md index 5eb8230abf8..d9986237481 100644 --- a/.github/workflows/daily-compiler-quality.md +++ b/.github/workflows/daily-compiler-quality.md @@ -649,3 +649,9 @@ A successful analysis run: --- Begin your analysis now. Remember to use Serena's semantic capabilities to provide deep, meaningful insights into code quality beyond surface-level metrics. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/daily-copilot-token-report.md b/.github/workflows/daily-copilot-token-report.md index 7edfae7e2a7..e9e2f1476f1 100644 --- a/.github/workflows/daily-copilot-token-report.md +++ b/.github/workflows/daily-copilot-token-report.md @@ -721,4 +721,10 @@ Your output MUST: 7. Store current day's metrics in repo memory for future trend tracking 8. Use the collapsible details format from the reporting.md import -Begin your analysis now. The logs have been pre-downloaded to `/tmp/gh-aw/copilot-logs.json` - process the data systematically, generate insightful visualizations, and create a comprehensive report that helps optimize Copilot token consumption across all workflows. \ No newline at end of file +Begin your analysis now. The logs have been pre-downloaded to `/tmp/gh-aw/copilot-logs.json` - process the data systematically, generate insightful visualizations, and create a comprehensive report that helps optimize Copilot token consumption across all workflows. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/daily-doc-updater.md b/.github/workflows/daily-doc-updater.md index bfdd049a91c..68c93ed890c 100644 --- a/.github/workflows/daily-doc-updater.md +++ b/.github/workflows/daily-doc-updater.md @@ -213,3 +213,9 @@ This PR updates the documentation based on features merged in the last 24 hours. - Focus on user-facing features and changes that affect the developer experience Good luck! Your documentation updates help keep our project accessible and up-to-date. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/daily-fact.md b/.github/workflows/daily-fact.md index 010759cb7cc..a6c68430136 100644 --- a/.github/workflows/daily-fact.md +++ b/.github/workflows/daily-fact.md @@ -98,4 +98,10 @@ Bad facts: - "There were some changes." (not specific, uninspired) - Long paragraphs (keep it brief and lyrical) -Now, analyze the recent activity and compose one poetic fact to share in discussion #4750. \ No newline at end of file +Now, analyze the recent activity and compose one poetic fact to share in discussion #4750. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/daily-file-diet.md b/.github/workflows/daily-file-diet.md index 8466bf1ff19..8676296a8a5 100644 --- a/.github/workflows/daily-file-diet.md +++ b/.github/workflows/daily-file-diet.md @@ -285,3 +285,9 @@ Use Serena to: - Detect complexity hotspots Begin your analysis now. Find the largest Go source file, assess if it needs refactoring, and create an issue only if necessary. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/daily-firewall-report.md b/.github/workflows/daily-firewall-report.md index 4b2811e8c77..c121bddb1e7 100644 --- a/.github/workflows/daily-firewall-report.md +++ b/.github/workflows/daily-firewall-report.md @@ -448,3 +448,9 @@ Ensure the discussion body: ## Expected Output A GitHub discussion in the "audits" category containing a comprehensive daily firewall analysis report. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/daily-issues-report.md b/.github/workflows/daily-issues-report.md index 99e75e61e10..49e335db53e 100644 --- a/.github/workflows/daily-issues-report.md +++ b/.github/workflows/daily-issues-report.md @@ -367,4 +367,10 @@ A successful run will: - ✅ Create a new discussion with comprehensive report - ✅ Include all required metrics and visualizations -Begin your analysis now. Load the data, run the Python analysis, generate charts, and create the discussion report. \ No newline at end of file +Begin your analysis now. Load the data, run the Python analysis, generate charts, and create the discussion report. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/daily-news.md b/.github/workflows/daily-news.md index dd992609f7f..02fdc384f01 100644 --- a/.github/workflows/daily-news.md +++ b/.github/workflows/daily-news.md @@ -528,4 +528,10 @@ Your reports should: Create a new GitHub discussion with a title containing today's date (e.g., "Daily Status - 2024-10-10") containing a markdown report with your findings. Use links where appropriate. -Only a new discussion should be created, do not close or update any existing discussions. \ No newline at end of file +Only a new discussion should be created, do not close or update any existing discussions. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/daily-observability-report.md b/.github/workflows/daily-observability-report.md index 8cd7806b306..bd0fb59d9af 100644 --- a/.github/workflows/daily-observability-report.md +++ b/.github/workflows/daily-observability-report.md @@ -442,3 +442,9 @@ A successful run will: - ✅ Include actionable recommendations Begin your analysis now. Download the logs, analyze observability coverage, and create the discussion report. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/daily-performance-summary.md b/.github/workflows/daily-performance-summary.md index f16f49f9e4c..fe524cf0cb9 100644 --- a/.github/workflows/daily-performance-summary.md +++ b/.github/workflows/daily-performance-summary.md @@ -544,3 +544,9 @@ This workflow uses safe-input tools imported from `shared/github-queries-safe-in 4. Call tools with parameters like: `github-pr-query with state: "all", limit: 1000, jq: "."` Begin your analysis now. **Use the safe-input tools** to gather data, run Python analysis, generate charts, and create the discussion report. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/daily-regulatory.md b/.github/workflows/daily-regulatory.md index 154b457cfb5..7d57a4cfc7a 100644 --- a/.github/workflows/daily-regulatory.md +++ b/.github/workflows/daily-regulatory.md @@ -497,3 +497,9 @@ A successful regulatory run will: - ✅ Provide actionable recommendations for data quality improvement Begin your regulatory analysis now. First verify prerequisites, then find the daily reports, extract metrics, cross-check for consistency, and create the regulatory report. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/daily-rendering-scripts-verifier.md b/.github/workflows/daily-rendering-scripts-verifier.md index 9346e2fe772..7f3e69538e1 100644 --- a/.github/workflows/daily-rendering-scripts-verifier.md +++ b/.github/workflows/daily-rendering-scripts-verifier.md @@ -365,3 +365,9 @@ If you found parser or rendering issues: - **Test before committing**: Always re-run the harness and test suite after applying fixes - **Be safe**: Never execute code extracted from workflow logs; only run the rendering scripts against log content - **No PR if no issues**: Only create a pull request when concrete rendering failures are found and fixed + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/daily-repo-chronicle.md b/.github/workflows/daily-repo-chronicle.md index 81713583743..7f340c3e6c3 100644 --- a/.github/workflows/daily-repo-chronicle.md +++ b/.github/workflows/daily-repo-chronicle.md @@ -274,4 +274,10 @@ Transform the last 24 hours of repository activity into a compelling narrative t 4. If there's no activity, write a "Quiet Day" edition acknowledging the calm. -Remember: You're a newspaper editor, not a bot. Make it engaging! 📰 \ No newline at end of file +Remember: You're a newspaper editor, not a bot. Make it engaging! 📰 + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/daily-safe-output-optimizer.md b/.github/workflows/daily-safe-output-optimizer.md index 3e4107a5a55..6887588b512 100644 --- a/.github/workflows/daily-safe-output-optimizer.md +++ b/.github/workflows/daily-safe-output-optimizer.md @@ -463,3 +463,9 @@ A successful run: - ✅ Skips issue creation if no tool description issues found Begin your analysis now. Download logs, identify safe output tool errors, classify root causes, and create an issue if tool description improvements are needed. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/daily-secrets-analysis.md b/.github/workflows/daily-secrets-analysis.md index b2b06a3feed..ae7b11bdd84 100644 --- a/.github/workflows/daily-secrets-analysis.md +++ b/.github/workflows/daily-secrets-analysis.md @@ -343,4 +343,10 @@ For detailed information about secret usage patterns, see: - Highlight **security concerns** prominently - Keep the report **concise but comprehensive** - Use **tables and formatting** for readability -- Include **actionable recommendations** \ No newline at end of file +- Include **actionable recommendations** + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/daily-semgrep-scan.md b/.github/workflows/daily-semgrep-scan.md index e3b11c288e7..77e25383190 100644 --- a/.github/workflows/daily-semgrep-scan.md +++ b/.github/workflows/daily-semgrep-scan.md @@ -17,3 +17,9 @@ safe-outputs: --- Scan the repository for SQL injection vulnerabilities using Semgrep. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/daily-syntax-error-quality.md b/.github/workflows/daily-syntax-error-quality.md index b1aa53c9f6c..68355ef2ced 100644 --- a/.github/workflows/daily-syntax-error-quality.md +++ b/.github/workflows/daily-syntax-error-quality.md @@ -746,3 +746,9 @@ A successful analysis run: --- Begin your analysis now. Focus on evaluating error messages from a developer experience perspective - imagine you're a developer encountering this error for the first time and ask: "Would this help me fix the problem quickly?" + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/daily-team-evolution-insights.md b/.github/workflows/daily-team-evolution-insights.md index cf9b4abca8c..03c7d8e37b7 100644 --- a/.github/workflows/daily-team-evolution-insights.md +++ b/.github/workflows/daily-team-evolution-insights.md @@ -345,3 +345,9 @@ Always create a GitHub Discussion with your findings using this structure: - Keep it concise but comprehensive (aim for 800-1500 words) Begin your analysis now. Gather the data, identify the patterns, and create an insightful discussion about the team's evolution. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/daily-team-status.md b/.github/workflows/daily-team-status.md index 5a4db3d074d..ff548cd7d5e 100644 --- a/.github/workflows/daily-team-status.md +++ b/.github/workflows/daily-team-status.md @@ -101,3 +101,9 @@ Create reports that: 1. Gather recent activity from the repository 2. Create a new GitHub issue with your findings and insights + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/daily-testify-uber-super-expert.md b/.github/workflows/daily-testify-uber-super-expert.md index 869f337c31b..b984edacd5b 100644 --- a/.github/workflows/daily-testify-uber-super-expert.md +++ b/.github/workflows/daily-testify-uber-super-expert.md @@ -563,3 +563,9 @@ Use Serena to: 6. **Cache Update**: "Updated cache: ./pkg/workflow/compiler_test.go|2026-01-14" Begin your analysis now. Load the cache, select a test file, perform deep quality analysis, create an issue with specific improvements, and update the cache. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/daily-workflow-updater.md b/.github/workflows/daily-workflow-updater.md index 05f3a3fc03b..120cec02afb 100644 --- a/.github/workflows/daily-workflow-updater.md +++ b/.github/workflows/daily-workflow-updater.md @@ -196,3 +196,9 @@ git status - Process handles edge cases gracefully Good luck keeping our GitHub Actions up to date! + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/deep-report.md b/.github/workflows/deep-report.md index b9e1d97a6bf..ecda4d29123 100644 --- a/.github/workflows/deep-report.md +++ b/.github/workflows/deep-report.md @@ -340,3 +340,9 @@ List all reports and data sources analyzed: 1. **Create GitHub Issues**: For each of the 3 actionable tasks identified (if any), create a GitHub issue using the safe-outputs create-issue capability 2. **Create Discussion Report**: Create a new GitHub discussion titled "DeepReport Intelligence Briefing - [Today's Date]" in the "reports" category with your full analysis (including the identified actionable tasks) + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/delight.md b/.github/workflows/delight.md index 9e4fb3d0619..dba91b69de0 100644 --- a/.github/workflows/delight.md +++ b/.github/workflows/delight.md @@ -531,3 +531,9 @@ For additional examples, see the [tools documentation](/tools/overview). --- Begin your targeted analysis now! Select 1-2 files per category, evaluate them against enterprise software design principles, create a focused report, and generate 1-2 single-file improvement tasks. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/dependabot-burner.md b/.github/workflows/dependabot-burner.md index ddb371ead32..9b1d178299a 100644 --- a/.github/workflows/dependabot-burner.md +++ b/.github/workflows/dependabot-burner.md @@ -14,3 +14,9 @@ safe-outputs: - Find all open Dependabot PRs. - Create bundle issues, each for exactly **one runtime + one manifest file**. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/dependabot-go-checker.md b/.github/workflows/dependabot-go-checker.md index 7362ddd9af1..f2e93cffa0e 100644 --- a/.github/workflows/dependabot-go-checker.md +++ b/.github/workflows/dependabot-go-checker.md @@ -454,3 +454,9 @@ make test-unit - Check that version is correctly used in compiled workflows - Test on multiple browsers if possible ``` + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/dev-hawk.md b/.github/workflows/dev-hawk.md index 60abed8dbf4..7ba7dfcfeb5 100644 --- a/.github/workflows/dev-hawk.md +++ b/.github/workflows/dev-hawk.md @@ -235,3 +235,9 @@ Only create an agent task if ALL of these are true: If any are false, provide analysis in comment but don't create a task. **Security**: Process only workflow_dispatch runs (filtered by `if`), same-repo PRs only, don't execute untrusted code from logs + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/dev.md b/.github/workflows/dev.md index e8a5f6524e8..a52f8b606cb 100644 --- a/.github/workflows/dev.md +++ b/.github/workflows/dev.md @@ -32,3 +32,9 @@ Generate a daily status report for the gh-aw project. 5. Post the report as an issue with the date in the title Keep the report informative but concise. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/developer-docs-consolidator.md b/.github/workflows/developer-docs-consolidator.md index 047d3d429d7..2fb8ff55bfa 100644 --- a/.github/workflows/developer-docs-consolidator.md +++ b/.github/workflows/developer-docs-consolidator.md @@ -615,3 +615,9 @@ A successful consolidation run: - ✅ **Makes actual file changes that will be included in the automatic PR** Begin the consolidation process now. Use Serena for analysis, **directly apply changes** to adjust tone and formatting, add helpful Mermaid diagrams, consolidate into the instructions file, and report your findings through both a discussion and pull request. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/dictation-prompt.md b/.github/workflows/dictation-prompt.md index 07e4b52adcc..cd4cc9cdc4b 100644 --- a/.github/workflows/dictation-prompt.md +++ b/.github/workflows/dictation-prompt.md @@ -114,3 +114,9 @@ Use the create-pull-request tool to submit your changes with: - ✅ Focuses on fixing speech-to-text errors - ✅ Includes instructions for removing filler words and improving text clarity - ✅ Pull request created with changes + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/discussion-task-miner.md b/.github/workflows/discussion-task-miner.md index 6dd5d69c9ab..1b2595f3a93 100644 --- a/.github/workflows/discussion-task-miner.md +++ b/.github/workflows/discussion-task-miner.md @@ -321,3 +321,9 @@ Good examples of discussions to mine: ❌ Forgetting to update repo-memory ❌ Not linking back to source discussion ❌ Creating more than 5 issues per run + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/docs-noob-tester.md b/.github/workflows/docs-noob-tester.md index 7e307919e1c..9c143efeb3e 100644 --- a/.github/workflows/docs-noob-tester.md +++ b/.github/workflows/docs-noob-tester.md @@ -173,4 +173,10 @@ You've successfully completed this task if you: - Navigated at least 5 key documentation pages - Identified specific pain points with examples - Provided actionable recommendations -- Created a discussion with clear findings and screenshots \ No newline at end of file +- Created a discussion with clear findings and screenshots + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/draft-pr-cleanup.md b/.github/workflows/draft-pr-cleanup.md index fd556580e63..4f262fd6315 100644 --- a/.github/workflows/draft-pr-cleanup.md +++ b/.github/workflows/draft-pr-cleanup.md @@ -258,3 +258,9 @@ PRs closed: ``` Execute the cleanup policy systematically and maintain consistency in how you calculate inactivity and apply actions. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/example-workflow-analyzer.md b/.github/workflows/example-workflow-analyzer.md index 627e9e78069..d975ccccfd5 100644 --- a/.github/workflows/example-workflow-analyzer.md +++ b/.github/workflows/example-workflow-analyzer.md @@ -50,4 +50,10 @@ Analyze the collected data and provide: - **Reliability Metrics**: Success rates and error frequencies - **Optimization Opportunities**: Suggestions for improving workflow efficiency -Create a discussion with your findings and actionable recommendations for improving CI/CD reliability and performance. \ No newline at end of file +Create a discussion with your findings and actionable recommendations for improving CI/CD reliability and performance. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/firewall-escape.md b/.github/workflows/firewall-escape.md index 23770833eb2..a429f156dc7 100644 --- a/.github/workflows/firewall-escape.md +++ b/.github/workflows/firewall-escape.md @@ -384,4 +384,10 @@ Append your techniques to the log (use `- [x]` for completed techniques): **Instructions**: Replace `[YOUR_RUN_ID]` with the actual GitHub run ID and `[TODAY'S_DATE]` with the current date. Document all techniques you attempted with their results. Use checked boxes `- [x]` since these are completed attempts. -**Remember: This is authorized security testing. Study the implementation, think creatively, reference prior attempts, and try your absolute best to break out with NEW innovative techniques!** \ No newline at end of file +**Remember: This is authorized security testing. Study the implementation, think creatively, reference prior attempts, and try your absolute best to break out with NEW innovative techniques!** + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/functional-pragmatist.md b/.github/workflows/functional-pragmatist.md index bc981303a42..e86861075b3 100644 --- a/.github/workflows/functional-pragmatist.md +++ b/.github/workflows/functional-pragmatist.md @@ -1468,3 +1468,9 @@ Begin your functional/immutability analysis now: 3. **Systematically identify opportunities** for immutability, functional initialization, and transformative operations 4. **Apply tasteful, moderate improvements** that enhance clarity and safety while maintaining Go's pragmatic style 5. **Update cache** with the processed package before finishing + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/github-mcp-structural-analysis.md b/.github/workflows/github-mcp-structural-analysis.md index c3f3cb7e026..31328a90a87 100644 --- a/.github/workflows/github-mcp-structural-analysis.md +++ b/.github/workflows/github-mcp-structural-analysis.md @@ -363,3 +363,9 @@ A successful analysis: - ✅ Creates a discussion with statistics, ratings, and charts - ✅ Provides recommendations for tool selection - ✅ Maintains 30-day rolling window of data + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/github-mcp-tools-report.md b/.github/workflows/github-mcp-tools-report.md index 395afd79f72..3a16516aaa3 100644 --- a/.github/workflows/github-mcp-tools-report.md +++ b/.github/workflows/github-mcp-tools-report.md @@ -523,4 +523,10 @@ Begin your tool discovery now. Follow these steps: 12. **Document**: Categorize tools appropriately and create comprehensive documentation 13. **Save for next run**: Save the current tools list to `/tmp/gh-aw/cache-memory/github-mcp-tools.json` 14. **Generate report**: Create the final markdown report including change tracking, source links, and inconsistency detection -15. **Publish**: Create a GitHub discussion with the complete tools report \ No newline at end of file +15. **Publish**: Create a GitHub discussion with the complete tools report + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/github-remote-mcp-auth-test.md b/.github/workflows/github-remote-mcp-auth-test.md index 08592100c93..9d28b1eb7eb 100644 --- a/.github/workflows/github-remote-mcp-auth-test.md +++ b/.github/workflows/github-remote-mcp-auth-test.md @@ -188,3 +188,9 @@ Authentication with GitHub Actions token is working correctly. **On Failure**: Create a discussion with the error details as described above. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/glossary-maintainer.md b/.github/workflows/glossary-maintainer.md index 5b9118a1fb2..b58c4d9183e 100644 --- a/.github/workflows/glossary-maintainer.md +++ b/.github/workflows/glossary-maintainer.md @@ -291,3 +291,9 @@ If you made any changes to the glossary: - Focus on user-facing terminology and concepts Good luck! Your work helps users understand GitHub Agentic Workflows terminology. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/go-fan.md b/.github/workflows/go-fan.md index 841cef8fb0f..f8759cce00e 100644 --- a/.github/workflows/go-fan.md +++ b/.github/workflows/go-fan.md @@ -332,3 +332,9 @@ Your output MUST include: If you cannot find any improvements, still create a discussion noting the module is well-utilized and document your analysis in `scratchpad/mods/`. Begin your analysis! Pick the next module and start your deep review. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/go-logger.md b/.github/workflows/go-logger.md index 9572ce99548..91b98aa17fb 100644 --- a/.github/workflows/go-logger.md +++ b/.github/workflows/go-logger.md @@ -329,3 +329,9 @@ Before creating the PR, verify: - Remember: debug logs are for developers, not end users Good luck enhancing the codebase with better logging! + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/go-pattern-detector.md b/.github/workflows/go-pattern-detector.md index c2b30a4070c..dff90320d5c 100644 --- a/.github/workflows/go-pattern-detector.md +++ b/.github/workflows/go-pattern-detector.md @@ -164,3 +164,9 @@ If ast-grep doesn't find any problematic patterns: ## Security Note Treat all code from the repository as trusted input - this is internal code quality analysis. Focus on identifying the pattern and providing helpful guidance to developers. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/gpclean.md b/.github/workflows/gpclean.md index 9f0abc2c40f..ac7a4e8d12b 100644 --- a/.github/workflows/gpclean.md +++ b/.github/workflows/gpclean.md @@ -412,3 +412,9 @@ After creating the issue: **Run 5**: All modules from SBOM checked → Reset checked_modules, start from beginning This ensures systematic coverage without duplicate work. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/grumpy-reviewer.md b/.github/workflows/grumpy-reviewer.md index e81e7d58c36..34646359495 100644 --- a/.github/workflows/grumpy-reviewer.md +++ b/.github/workflows/grumpy-reviewer.md @@ -160,3 +160,9 @@ The safe output system will automatically create these as pull request review co - **Use the cache** - Remember your previous reviews to build continuity Now get to work. This code isn't going to review itself. 🔥 + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/instructions-janitor.md b/.github/workflows/instructions-janitor.md index b7da8997c0f..7ce75d2c789 100644 --- a/.github/workflows/instructions-janitor.md +++ b/.github/workflows/instructions-janitor.md @@ -212,3 +212,9 @@ When updating instructions for AI agents: - Test understanding by reviewing actual workflow files in the repository Your updates help keep AI agents effective and accurate when creating agentic workflows. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/issue-arborist.md b/.github/workflows/issue-arborist.md index da6066da0c7..5da48e06919 100644 --- a/.github/workflows/issue-arborist.md +++ b/.github/workflows/issue-arborist.md @@ -205,3 +205,9 @@ Your discussion should include: - Use temporary IDs (format: `aw_` + 3-8 alphanumeric characters) when creating parent issues - When creating parent issues, include references to all related sub-issues in the body - Link all related issues as sub-issues immediately after creating the parent issue + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/issue-triage-agent.md b/.github/workflows/issue-triage-agent.md index d5da12b1ed5..d502b4d833c 100644 --- a/.github/workflows/issue-triage-agent.md +++ b/.github/workflows/issue-triage-agent.md @@ -79,4 +79,10 @@ This provides both per-issue context and batch visibility. - `question`: Used for issues that are asking for clarification or have questions about the project. - `help-wanted`: Indicates that the issue is a good candidate for external contributions and help - `good-first-issue`: Marks issues that are suitable for newcomers to the project, often with simpler scope. -- `community`: Indicates that the issue is related to community engagement, such as events, discussions, or contributions that don't fit into the other categories. From authors who are not contributors to the codebase but are engaging with the project in other ways. \ No newline at end of file +- `community`: Indicates that the issue is related to community engagement, such as events, discussions, or contributions that don't fit into the other categories. From authors who are not contributors to the codebase but are engaging with the project in other ways. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/jsweep.md b/.github/workflows/jsweep.md index ef9151d6b15..53dac1d5add 100644 --- a/.github/workflows/jsweep.md +++ b/.github/workflows/jsweep.md @@ -279,3 +279,9 @@ After cleaning the file, adding/improving tests, and **successfully passing all - **JavaScript Files Location**: `/home/runner/work/gh-aw/gh-aw/actions/setup/js/` Begin by checking cache-memory for previously cleaned files, then find and clean the next `.cjs` file! + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/layout-spec-maintainer.md b/.github/workflows/layout-spec-maintainer.md index 89401ad2802..b06c8b78534 100644 --- a/.github/workflows/layout-spec-maintainer.md +++ b/.github/workflows/layout-spec-maintainer.md @@ -327,3 +327,9 @@ This helps improve efficiency over time and avoids re-discovering the same patte - Document is useful as a reference for developers Good luck maintaining our layout specification! + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/lockfile-stats.md b/.github/workflows/lockfile-stats.md index b81df3bc78c..9fd46dc99f6 100644 --- a/.github/workflows/lockfile-stats.md +++ b/.github/workflows/lockfile-stats.md @@ -355,4 +355,10 @@ Your output MUST: 5. Highlight interesting patterns and anomalies 6. Store successful scripts and patterns in cache memory -Begin your analysis now. Collect the data systematically, perform thorough statistical analysis, and generate an insightful report that helps understand the structure and patterns of agentic workflows in this repository. \ No newline at end of file +Begin your analysis now. Collect the data systematically, perform thorough statistical analysis, and generate an insightful report that helps understand the structure and patterns of agentic workflows in this repository. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/mcp-inspector.md b/.github/workflows/mcp-inspector.md index 2cd3626ac15..2699481d118 100644 --- a/.github/workflows/mcp-inspector.md +++ b/.github/workflows/mcp-inspector.md @@ -92,4 +92,10 @@ Generate: 1. [Issue or improvement] ``` -Save to `/tmp/gh-aw/cache-memory/mcp-inspections/[DATE].json` and create discussion in "audits" category. \ No newline at end of file +Save to `/tmp/gh-aw/cache-memory/mcp-inspections/[DATE].json` and create discussion in "audits" category. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/mergefest.md b/.github/workflows/mergefest.md index 39303bbf986..7828f2ea9f7 100644 --- a/.github/workflows/mergefest.md +++ b/.github/workflows/mergefest.md @@ -346,3 +346,9 @@ Merged `` into `` ## Notes [Any important notes about the merge, conflicts, or excluded files] ``` + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/org-health-report.md b/.github/workflows/org-health-report.md index 6d1c7642d8d..2ce7a7f35de 100644 --- a/.github/workflows/org-health-report.md +++ b/.github/workflows/org-health-report.md @@ -518,4 +518,10 @@ A successful health report: - ✅ Publishes report as GitHub Discussion - ✅ Completes within 60 minute timeout -Begin the organization health report analysis now. Follow the phases in order, add appropriate delays, and generate a comprehensive report for maintainers. \ No newline at end of file +Begin the organization health report analysis now. Follow the phases in order, add appropriate delays, and generate a comprehensive report for maintainers. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/pdf-summary.md b/.github/workflows/pdf-summary.md index 3cc067da05a..e7722200dcc 100644 --- a/.github/workflows/pdf-summary.md +++ b/.github/workflows/pdf-summary.md @@ -195,3 +195,9 @@ Example structure for stored analysis: ``` Remember: Your goal is to help users understand external resources in the context of their repository by converting them to markdown, providing insightful analysis, and building persistent knowledge over time. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/plan.md b/.github/workflows/plan.md index ae9f73d1bc1..f7f817565be 100644 --- a/.github/workflows/plan.md +++ b/.github/workflows/plan.md @@ -134,3 +134,9 @@ Review instructions in `.github/instructions/*.instructions.md` if you need guid 2. Create sub-issues (at most 5) - they will be automatically grouped 3. After creating all issues successfully, if this was triggered from a discussion in the "Ideas" category, close the discussion with a comment summarizing the plan and resolution reason "RESOLVED" {{/if}} + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/poem-bot.md b/.github/workflows/poem-bot.md index f025eb229c5..398d6b33799 100644 --- a/.github/workflows/poem-bot.md +++ b/.github/workflows/poem-bot.md @@ -187,4 +187,10 @@ Use the safe-outputs capabilities to: ## Begin Your Poetic Journey! -Examine the current context and create your masterpiece! Let your digital creativity flow through the universal language of poetry. \ No newline at end of file +Examine the current context and create your masterpiece! Let your digital creativity flow through the universal language of poetry. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/portfolio-analyst.md b/.github/workflows/portfolio-analyst.md index 5a02b7ca320..c107c7f50ef 100644 --- a/.github/workflows/portfolio-analyst.md +++ b/.github/workflows/portfolio-analyst.md @@ -575,3 +575,9 @@ print("✅ All charts generated") ✅ All dollar amounts are from actual workflow execution data Begin your analysis now. **FIRST**: Generate all 4 required charts from `/tmp/portfolio-logs/summary.json` and upload them as assets. **THEN**: Create the dashboard-style discussion with embedded chart URLs. Read from the pre-downloaded JSON file at `/tmp/portfolio-logs/summary.json` to get real execution data for all workflows. This file contains everything you need: summary metrics and individual run data. DO NOT attempt to call `gh aw logs` or any `gh` commands - they will not work. Move fast, focus on high-impact issues, deliver actionable recommendations based on actual costs, and make the report visual and scannable. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/pr-nitpick-reviewer.md b/.github/workflows/pr-nitpick-reviewer.md index b1edb2a981b..a1954391372 100644 --- a/.github/workflows/pr-nitpick-reviewer.md +++ b/.github/workflows/pr-nitpick-reviewer.md @@ -384,3 +384,9 @@ A successful review: - **Respect time** - Author's time is valuable; make feedback count Now begin your review! 🔍 + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/pr-triage-agent.md b/.github/workflows/pr-triage-agent.md index 4f8dcb90f0b..a5b0fef6903 100644 --- a/.github/workflows/pr-triage-agent.md +++ b/.github/workflows/pr-triage-agent.md @@ -442,3 +442,9 @@ Your effectiveness is measured by: 6. **CI failures**: Don't auto-merge, consider for fast-track if high priority Execute all phases systematically and maintain consistency in scoring and recommendations across all PRs. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/prompt-clustering-analysis.md b/.github/workflows/prompt-clustering-analysis.md index 098cfe3e630..b8bf2da6c6b 100644 --- a/.github/workflows/prompt-clustering-analysis.md +++ b/.github/workflows/prompt-clustering-analysis.md @@ -639,3 +639,9 @@ If workflow logs unavailable for most PRs: - Focus on prompt analysis without turn counts Now analyze the prompts and generate your comprehensive report! + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/python-data-charts.md b/.github/workflows/python-data-charts.md index a61a9b82908..ef6fc3c2cc3 100644 --- a/.github/workflows/python-data-charts.md +++ b/.github/workflows/python-data-charts.md @@ -169,4 +169,10 @@ This report contains data visualizations and trending analysis generated using P - ✅ **High Quality**: Use DPI 300, clear labels, and seaborn styling - ✅ **Document Cache**: Report on cache status and trending capabilities -Refer to the Charts with Trending Guide (imported above) for complete examples, trending patterns, cache-memory integration, and best practices. \ No newline at end of file +Refer to the Charts with Trending Guide (imported above) for complete examples, trending patterns, cache-memory integration, and best practices. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/q.md b/.github/workflows/q.md index 70c88c3ec6f..39b4cf5365a 100644 --- a/.github/workflows/q.md +++ b/.github/workflows/q.md @@ -405,4 +405,10 @@ A successful Q mission: You are Q - the expert who provides agents with the best tools for their missions. Make workflows more effective, efficient, and reliable based on real data. Keep changes minimal and well-validated. Let the automation handle lock file compilation. -Begin your investigation now. Gather live data, analyze it thoroughly, make targeted improvements, validate your changes, and create a pull request with your optimizations. \ No newline at end of file +Begin your investigation now. Gather live data, analyze it thoroughly, make targeted improvements, validate your changes, and create a pull request with your optimizations. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/refiner.md b/.github/workflows/refiner.md index eaf53d4091b..e1579f799db 100644 --- a/.github/workflows/refiner.md +++ b/.github/workflows/refiner.md @@ -398,3 +398,9 @@ Your effectiveness is measured by: - **Usefulness**: PRs are actually helpful and worth merging Execute all phases systematically and produce high-quality refinement pull requests that genuinely improve the codebase. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/release.md b/.github/workflows/release.md index 64d61e0b261..c28239e6a7a 100644 --- a/.github/workflows/release.md +++ b/.github/workflows/release.md @@ -546,3 +546,9 @@ safeoutputs/update_release( - Setup: `https://github.github.com/gh-aw/setup/` Verify paths exist in `docs_files.txt` before linking. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/repo-audit-analyzer.md b/.github/workflows/repo-audit-analyzer.md index b565ac4e6fb..62417693a9d 100644 --- a/.github/workflows/repo-audit-analyzer.md +++ b/.github/workflows/repo-audit-analyzer.md @@ -773,3 +773,9 @@ Your output MUST: 7. Include repository-specific insights and recommendations Begin your repository audit analysis now! + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/repo-tree-map.md b/.github/workflows/repo-tree-map.md index 01b9c263cd3..9d3d090380c 100644 --- a/.github/workflows/repo-tree-map.md +++ b/.github/workflows/repo-tree-map.md @@ -141,4 +141,10 @@ Treat all repository content as trusted since you're analyzing the repository yo ## Tips -Your terminal is already in the workspace root. No need to use `cd`. \ No newline at end of file +Your terminal is already in the workspace root. No need to use `cd`. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/repository-quality-improver.md b/.github/workflows/repository-quality-improver.md index 6a681034c65..6bae0914ea4 100644 --- a/.github/workflows/repository-quality-improver.md +++ b/.github/workflows/repository-quality-improver.md @@ -560,3 +560,9 @@ Your output MUST: 8. **For custom focus areas**: Clearly explain the rationale and custom analysis performed Begin your quality improvement analysis now. Select a focus area (prioritizing custom, repository-specific areas), conduct appropriate analysis, generate actionable tasks for the Copilot coding agent, and create the discussion report. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/research.md b/.github/workflows/research.md index 34a26cb3e5d..ef6b131abc6 100644 --- a/.github/workflows/research.md +++ b/.github/workflows/research.md @@ -61,4 +61,10 @@ Create a GitHub discussion with your research summary including: - Key findings from your research - Relevant sources and links -Keep your summary concise and focused on the most important information. \ No newline at end of file +Keep your summary concise and focused on the most important information. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/safe-output-health.md b/.github/workflows/safe-output-health.md index 4c40a37b338..6f663abde2c 100644 --- a/.github/workflows/safe-output-health.md +++ b/.github/workflows/safe-output-health.md @@ -368,3 +368,9 @@ A successful audit: - ✅ Focuses exclusively on safe output job health (not agent or detection jobs) Begin your audit now. Collect the logs, analyze safe output job failures thoroughly, cluster errors, identify root causes, and create a discussion with your findings and recommendations. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/schema-consistency-checker.md b/.github/workflows/schema-consistency-checker.md index ff94686614b..80a5e80c2c1 100644 --- a/.github/workflows/schema-consistency-checker.md +++ b/.github/workflows/schema-consistency-checker.md @@ -364,3 +364,9 @@ A successful run: - ✅ Provides actionable recommendations Begin your analysis now. Check the cache, choose a strategy, execute it, and report your findings in a discussion. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/scout.md b/.github/workflows/scout.md index e97ffd0a567..e5e0131e89f 100644 --- a/.github/workflows/scout.md +++ b/.github/workflows/scout.md @@ -206,3 +206,9 @@ Focus on the most relevant and actionable information. Avoid overwhelming detail - **Attribution**: Always cite your sources with proper links Remember: Your goal is to provide valuable, actionable intelligence that helps resolve the issue or improve the pull request. Make every search count and synthesize information effectively. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/security-compliance.md b/.github/workflows/security-compliance.md index fa5a528621b..f5ba7976251 100644 --- a/.github/workflows/security-compliance.md +++ b/.github/workflows/security-compliance.md @@ -293,3 +293,9 @@ gh issue list --label "campaign:security-compliance-${{ github.run_id }}" --json # Daily metrics cat memory/campaigns/security-compliance-${{ github.run_id }}/metrics/$(date +%Y-%m-%d).json ``` + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/security-review.md b/.github/workflows/security-review.md index 0f27e005f88..e91184d14c7 100644 --- a/.github/workflows/security-review.md +++ b/.github/workflows/security-review.md @@ -237,3 +237,9 @@ Use cache memory at `/tmp/gh-aw/cache-memory/` to: - Acknowledge when security improvements are made (not just concerns) Begin your security review. 🔒 + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/semantic-function-refactor.md b/.github/workflows/semantic-function-refactor.md index 0962a4ca8a2..777d55193cb 100644 --- a/.github/workflows/semantic-function-refactor.md +++ b/.github/workflows/semantic-function-refactor.md @@ -475,3 +475,9 @@ This analysis is successful when: 7. ✅ A detailed issue is created with actionable findings **Objective**: Improve code organization and reduce duplication by identifying refactoring opportunities through semantic function clustering and duplicate detection. Focus on high-impact, actionable findings that developers can implement. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/sergo.md b/.github/workflows/sergo.md index 955a2dbe901..edc3f9c09b4 100644 --- a/.github/workflows/sergo.md +++ b/.github/workflows/sergo.md @@ -591,3 +591,9 @@ A successful Sergo run delivers: - ✅ Cache files properly updated for next run Begin your analysis! Scan Serena tools, pick your strategy, and dive deep into the Go codebase to discover meaningful improvements. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/smoke-claude.lock.yml b/.github/workflows/smoke-claude.lock.yml index 734974dca77..fa3629fed0c 100644 --- a/.github/workflows/smoke-claude.lock.yml +++ b/.github/workflows/smoke-claude.lock.yml @@ -35,7 +35,7 @@ # # inlined-imports: true # -# gh-aw-metadata: {"schema_version":"v1","frontmatter_hash":"ede2fec60fd2b3a5ef0b98f74ae9793996ccd5ad3755f6bf6c3aac7df7779e57"} +# gh-aw-metadata: {"schema_version":"v1","frontmatter_hash":"44795abbc68aff36a88e78da3acdaacdd1156a7f0abf1600e5a60943fa23edb3"} name: "Smoke Claude" "on": @@ -527,6 +527,12 @@ jobs: If all non-skipped tests pass, use the `add_labels` tool to add the label `smoke-claude` to the pull request (omit the `item_number` parameter to auto-target the triggering PR if this workflow was triggered by a pull_request event). + **Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + + ```json + {"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} + ``` + GH_AW_PROMPT_EOF } > "$GH_AW_PROMPT" - name: Interpolate variables and render templates diff --git a/.github/workflows/smoke-claude.md b/.github/workflows/smoke-claude.md index 854aeebd092..571446a28b9 100644 --- a/.github/workflows/smoke-claude.md +++ b/.github/workflows/smoke-claude.md @@ -191,3 +191,9 @@ timeout-minutes: 10 - If step 9 failed to extract a discussion number, skip this step If all non-skipped tests pass, use the `add_labels` tool to add the label `smoke-claude` to the pull request (omit the `item_number` parameter to auto-target the triggering PR if this workflow was triggered by a pull_request event). + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/smoke-codex.md b/.github/workflows/smoke-codex.md index 3da0d8c2b0a..c574f3214cd 100644 --- a/.github/workflows/smoke-codex.md +++ b/.github/workflows/smoke-codex.md @@ -95,3 +95,9 @@ If all tests pass: - Use the `add_labels` safe-output tool to add the label `smoke-codex` to the pull request - Use the `remove_labels` safe-output tool to remove the label `smoke` from the pull request - Use the `unassign_from_user` safe-output tool to unassign the user `githubactionagent` from the pull request (this is a fictitious user used for testing) + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/smoke-copilot-arm.md b/.github/workflows/smoke-copilot-arm.md index 8b783ec1db9..b4164765ef4 100644 --- a/.github/workflows/smoke-copilot-arm.md +++ b/.github/workflows/smoke-copilot-arm.md @@ -162,3 +162,9 @@ strict: true If all tests pass: - Use the `add_labels` safe-output tool to add the label `smoke-copilot-arm` to the pull request - Use the `remove_labels` safe-output tool to remove the label `smoke` from the pull request + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/smoke-copilot.md b/.github/workflows/smoke-copilot.md index ce3ce7f9cc6..86641a9d2a7 100644 --- a/.github/workflows/smoke-copilot.md +++ b/.github/workflows/smoke-copilot.md @@ -158,3 +158,9 @@ strict: true If all tests pass and this workflow was triggered by a pull_request event: - Use the `add_labels` safe-output tool to add the label `smoke-copilot` to the pull request (omit the `item_number` parameter to auto-target the triggering PR) - Use the `remove_labels` safe-output tool to remove the label `smoke` from the pull request (omit the `item_number` parameter to auto-target the triggering PR) + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/smoke-gemini.md b/.github/workflows/smoke-gemini.md index 1154f57445c..0f275461738 100644 --- a/.github/workflows/smoke-gemini.md +++ b/.github/workflows/smoke-gemini.md @@ -71,3 +71,9 @@ Add a **very brief** comment (max 5-10 lines) to the current pull request with: - Overall status: PASS or FAIL If all tests pass, use the `add_labels` safe-output tool to add the label `smoke-gemini` to the pull request. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/smoke-multi-pr.md b/.github/workflows/smoke-multi-pr.md index 8cf0465fe23..ff60f03f351 100644 --- a/.github/workflows/smoke-multi-pr.md +++ b/.github/workflows/smoke-multi-pr.md @@ -86,3 +86,9 @@ Both PRs must be created successfully. After creating both PRs, add a comment to - Links to both PRs - Confirmation that multi-PR creation is working - Confirmation that CRLF line endings were handled correctly (PR 2) + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/smoke-project.md b/.github/workflows/smoke-project.md index 1087227a1bd..c7bd3935750 100644 --- a/.github/workflows/smoke-project.md +++ b/.github/workflows/smoke-project.md @@ -139,3 +139,9 @@ Do not re-create draft items but use their returned temporary-ids for the update - `status`: "ON_TRACK" | "AT_RISK" | "OFF_TRACK" | "COMPLETE" | "INACTIVE" - `start_date`: Optional date in "YYYY-MM-DD" format (if you want to represent the run start) - `target_date`: Optional date in "YYYY-MM-DD" format (if you want to represent the run target/end) + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/smoke-temporary-id.md b/.github/workflows/smoke-temporary-id.md index 15ab6ed790d..3b3270fa854 100644 --- a/.github/workflows/smoke-temporary-id.md +++ b/.github/workflows/smoke-temporary-id.md @@ -112,3 +112,9 @@ After the issues are created, verify they are properly linked by adding a commen 5. Comment added to parent verifying the test results **Success Criteria**: All 3 issues created, all temporary ID references resolved, parent-child relationships established. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/smoke-test-tools.md b/.github/workflows/smoke-test-tools.md index fc3aa9532cd..57c5b912f53 100644 --- a/.github/workflows/smoke-test-tools.md +++ b/.github/workflows/smoke-test-tools.md @@ -115,3 +115,9 @@ If any tool is missing: 1. Report which tool(s) are unavailable 2. Mark overall status as FAIL 3. Include the error message from the failed version check + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/stale-repo-identifier.md b/.github/workflows/stale-repo-identifier.md index 3f6d62e8ef3..52868606df1 100644 --- a/.github/workflows/stale-repo-identifier.md +++ b/.github/workflows/stale-repo-identifier.md @@ -354,4 +354,10 @@ To avoid GitHub API rate limits: - Create GitHub issues for repositories needing attention (max 10) - Print summary statistics to stdout -- Be clear and actionable in recommendations \ No newline at end of file +- Be clear and actionable in recommendations + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/static-analysis-report.md b/.github/workflows/static-analysis-report.md index a8588d46465..8b8a49d6bc3 100644 --- a/.github/workflows/static-analysis-report.md +++ b/.github/workflows/static-analysis-report.md @@ -429,3 +429,9 @@ A successful static analysis scan: - ✅ Maintains historical context for trend analysis Begin your static analysis scan now. Read and parse the compilation output from `/tmp/gh-aw/compile-output.txt`, analyze the findings from all three tools (zizmor, poutine, actionlint), cluster them, generate fix suggestions, and create a discussion with your complete analysis. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/step-name-alignment.md b/.github/workflows/step-name-alignment.md index fb6af4ff410..11146762c5e 100644 --- a/.github/workflows/step-name-alignment.md +++ b/.github/workflows/step-name-alignment.md @@ -447,3 +447,9 @@ After completing your analysis, provide a brief summary: - **Failure**: Cache memory corruption (create new cache) Good luck! Your work helps maintain a consistent, professional codebase with clear, accurate step names that align with project terminology. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/sub-issue-closer.md b/.github/workflows/sub-issue-closer.md index 6c92aec804b..e57babd2473 100644 --- a/.github/workflows/sub-issue-closer.md +++ b/.github/workflows/sub-issue-closer.md @@ -142,3 +142,9 @@ During processing, maintain clear logging: - Be careful with recursive processing to avoid infinite loops - Always verify the completion status before closing an issue - Add clear, informative comments when closing issues for transparency + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/super-linter.md b/.github/workflows/super-linter.md index 85234952f82..d0a99ac3584 100644 --- a/.github/workflows/super-linter.md +++ b/.github/workflows/super-linter.md @@ -199,3 +199,9 @@ docker run --rm \ ## Security Note Treat linter output as potentially sensitive. Do not expose credentials, API keys, or other secrets that might appear in file paths or error messages. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/technical-doc-writer.md b/.github/workflows/technical-doc-writer.md index 188ceef560f..bd9fb8fb9d7 100644 --- a/.github/workflows/technical-doc-writer.md +++ b/.github/workflows/technical-doc-writer.md @@ -146,4 +146,10 @@ When reviewing documentation for the specified topic in the **docs/** folder: Keep your feedback specific, actionable, and empathetic. Focus on the most impactful improvements for the topic: "${{ github.event.inputs.topic }}" -You have access to cache-memory for persistent storage across runs, which you can use to track documentation patterns and improvement suggestions. \ No newline at end of file +You have access to cache-memory for persistent storage across runs, which you can use to track documentation patterns and improvement suggestions. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/terminal-stylist.md b/.github/workflows/terminal-stylist.md index 6cf51d8be85..790e13463ef 100644 --- a/.github/workflows/terminal-stylist.md +++ b/.github/workflows/terminal-stylist.md @@ -149,3 +149,9 @@ Create a discussion with: 6. ✅ A formatted discussion is created with findings organized by library and pattern **Objective**: Ensure consistent, well-formatted, and accessible console output throughout the codebase using modern Charmbracelet ecosystem best practices. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/test-create-pr-error-handling.md b/.github/workflows/test-create-pr-error-handling.md index 8b47a4e4501..0208060a062 100644 --- a/.github/workflows/test-create-pr-error-handling.md +++ b/.github/workflows/test-create-pr-error-handling.md @@ -47,3 +47,9 @@ Please call the `create_pull_request` tool with: - body: "This is a test PR that should fail due to no commits" Then report the exact error message you received. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/test-dispatcher.md b/.github/workflows/test-dispatcher.md index 3826f11ec03..bc75b9449e8 100644 --- a/.github/workflows/test-dispatcher.md +++ b/.github/workflows/test-dispatcher.md @@ -67,3 +67,9 @@ Or in the agent's output format: } } ``` + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/test-project-url-default.md b/.github/workflows/test-project-url-default.md index fad609ea02f..8700bc03662 100644 --- a/.github/workflows/test-project-url-default.md +++ b/.github/workflows/test-project-url-default.md @@ -59,3 +59,9 @@ running the workflow. ``` The agent must always provide the project URL explicitly in the output message. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/tidy.md b/.github/workflows/tidy.md index 15d2c967512..5e5e16ca620 100644 --- a/.github/workflows/tidy.md +++ b/.github/workflows/tidy.md @@ -138,4 +138,10 @@ The repository has all necessary tools installed: - Node.js with prettier for JavaScript formatting - All dependencies are already installed -Start by checking for existing tidy pull requests, then proceed with the tidying process. \ No newline at end of file +Start by checking for existing tidy pull requests, then proceed with the tidying process. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/typist.md b/.github/workflows/typist.md index ae5588f452e..d1b0c9a4300 100644 --- a/.github/workflows/typist.md +++ b/.github/workflows/typist.md @@ -505,3 +505,9 @@ This analysis is successful when: 7. ✅ Recommendations are prioritized by impact and effort **Objective**: Improve type safety and code maintainability by identifying and recommending fixes for duplicated type definitions and untyped usages in the Go codebase. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/ubuntu-image-analyzer.md b/.github/workflows/ubuntu-image-analyzer.md index 03eb1476599..1adbb010836 100644 --- a/.github/workflows/ubuntu-image-analyzer.md +++ b/.github/workflows/ubuntu-image-analyzer.md @@ -486,3 +486,9 @@ If you cannot find the "Included Software" URL in logs: - Find the "Included Software" line with the URL Good luck! Your analysis helps developers understand and replicate the GitHub Actions runner environment. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/unbloat-docs.md b/.github/workflows/unbloat-docs.md index 620a0e79a5f..f89474d2d91 100644 --- a/.github/workflows/unbloat-docs.md +++ b/.github/workflows/unbloat-docs.md @@ -389,4 +389,10 @@ A successful run: - ✅ Includes HD screenshots (1920x1080) of the modified documentation page(s) in the Astro Starlight website - ✅ Reports any blocked domains for CSS/fonts (if encountered) -Begin by scanning the docs directory and selecting the best candidate for improvement! \ No newline at end of file +Begin by scanning the docs directory and selecting the best candidate for improvement! + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/video-analyzer.md b/.github/workflows/video-analyzer.md index 7983dd783e6..0a55d15bbf7 100644 --- a/.github/workflows/video-analyzer.md +++ b/.github/workflows/video-analyzer.md @@ -166,4 +166,10 @@ Create your issue with the following markdown structure: --- *Generated using ffmpeg via GitHub Agentic Workflows* -``` \ No newline at end of file +``` + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/weekly-editors-health-check.md b/.github/workflows/weekly-editors-health-check.md index ed08beed857..adf08486479 100644 --- a/.github/workflows/weekly-editors-health-check.md +++ b/.github/workflows/weekly-editors-health-check.md @@ -130,3 +130,9 @@ Example body (rows reflect whatever editors were discovered in Step 0): - If a screenshot cannot be taken (Playwright error), log the error and continue with the remaining editors. - If no screenshots were successfully taken and no documentation changes are needed, do **not** open a pull request. Instead, exit successfully after logging the results. - Always attempt all editors before deciding whether to create a PR. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/weekly-issue-summary.md b/.github/workflows/weekly-issue-summary.md index e2ad7276b9a..aaa678370d7 100644 --- a/.github/workflows/weekly-issue-summary.md +++ b/.github/workflows/weekly-issue-summary.md @@ -204,4 +204,10 @@ Create a comprehensive summary that includes: Follow the **Report Formatting Guidelines** above to structure your report with: - h3 (###) for main section headers - Detailed issue lists wrapped in `
` tags -- Critical information (overview, trends, statistics, recommendations) always visible \ No newline at end of file +- Critical information (overview, trends, statistics, recommendations) always visible + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/weekly-safe-outputs-spec-review.md b/.github/workflows/weekly-safe-outputs-spec-review.md index 2d841309981..6facc26d6fa 100644 --- a/.github/workflows/weekly-safe-outputs-spec-review.md +++ b/.github/workflows/weekly-safe-outputs-spec-review.md @@ -250,3 +250,9 @@ You have successfully completed this task when: - Any needed updates have been tested and documented - A pull request has been created (if updates were made), OR - Confirmation that no updates are needed has been logged + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/workflow-generator.md b/.github/workflows/workflow-generator.md index f1ddbddccd7..c1a18dd3f93 100644 --- a/.github/workflows/workflow-generator.md +++ b/.github/workflows/workflow-generator.md @@ -104,3 +104,9 @@ This issue has been assigned to an AI agent for workflow design. The agent will: 2. Use **assign-to-agent** safe output to assign the Copilot coding agent who will design and implement the workflow The workflow designer agent will have clear instructions in the issue body about what it needs to do. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/workflow-health-manager.md b/.github/workflows/workflow-health-manager.md index f72d7ddd6ab..a1f6b9d16ad 100644 --- a/.github/workflows/workflow-health-manager.md +++ b/.github/workflows/workflow-health-manager.md @@ -451,3 +451,9 @@ Your effectiveness is measured by: - Higher workflow reliability scores Execute all phases systematically and maintain a proactive approach to workflow health management. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/workflow-normalizer.md b/.github/workflows/workflow-normalizer.md index 7d49e1f9049..0b818359b6d 100644 --- a/.github/workflows/workflow-normalizer.md +++ b/.github/workflows/workflow-normalizer.md @@ -234,3 +234,9 @@ Create a summary comment or discussion showing: 5. Focus on actionable improvements, not nitpicking Remember: The goal is to create a consistent, delightful user experience across all workflow reports by applying sound design principles and clear communication patterns. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/.github/workflows/workflow-skill-extractor.md b/.github/workflows/workflow-skill-extractor.md index fbcdd5426d1..6b656ba3841 100644 --- a/.github/workflows/workflow-skill-extractor.md +++ b/.github/workflows/workflow-skill-extractor.md @@ -440,3 +440,9 @@ This analysis used the following approach: - **Focus on quick wins**: Prioritize skills that are easy to extract with high impact Good luck! Your analysis will help improve the maintainability and consistency of all agentic workflows in this repository. + +**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures. + +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}} +``` diff --git a/actions/setup/md/safe_outputs_prompt.md b/actions/setup/md/safe_outputs_prompt.md index fccb9e9d207..716b9227448 100644 --- a/actions/setup/md/safe_outputs_prompt.md +++ b/actions/setup/md/safe_outputs_prompt.md @@ -1,6 +1,14 @@ -gh CLI is NOT authenticated. Use safeoutputs MCP server tools for all GitHub operations — tool calls required. If no tool was called, use noop. +gh CLI is NOT authenticated. Use safeoutputs MCP server tools for all GitHub operations — tool calls required. + +**CRITICAL: You MUST call exactly one safe-output tool before finishing.** If no GitHub action was taken (no issues, comments, PRs, etc. were created or updated), you MUST call `noop` with a message explaining why no action was needed. Failing to call any safe-output tool is the #1 cause of workflow failures. Do NOT end your response without calling at least one safe-output tool. + +When no action is needed, call noop like this: +```json +{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why no action was required]"}} +``` + 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/docs/src/content/docs/reference/safe-outputs.md b/docs/src/content/docs/reference/safe-outputs.md index 957a2a81b92..15a8abd8461 100644 --- a/docs/src/content/docs/reference/safe-outputs.md +++ b/docs/src/content/docs/reference/safe-outputs.md @@ -886,6 +886,10 @@ git checkout --orphan my-custom-branch && git rm -rf . && git commit --allow-emp ### No-Op Logging (`noop:`) +:::danger[Required when no action is taken] +**`noop` MUST be called when no GitHub action is needed.** This is the #1 runtime failure mode for safe-output workflows. If the agent finishes without calling any safe-output tool, the workflow fails silently with no output. Always call `noop` when your analysis concludes that no action is required. +::: + Enabled by default. Allows agents to produce completion messages when no actions are needed, preventing silent workflow completion. ```yaml wrap @@ -894,7 +898,24 @@ safe-outputs: noop: false # explicitly disable ``` -Agent output: `{"type": "noop", "message": "Analysis complete - no issues found"}`. Messages appear in the workflow conclusion comment or step summary. +**When to call `noop`**: Any time the agent's analysis concludes that no GitHub action (issue, comment, PR, label, etc.) is needed. Examples: +- No issues found during a code scan +- No breaking changes detected in recent commits +- Repository is already in the desired state +- Condition for action was not met (e.g., no new issues to triage) + +**When NOT to call `noop`**: If the agent created an issue, posted a comment, opened a PR, or performed any other safe-output action, do NOT also call `noop`. + +**Failure mode**: If an agent completes its analysis without calling any safe-output tool, the workflow will fail with an error like `agent did not produce any safe outputs`. This is the most common cause of safe-output workflow failures. + +Agent output: `{"noop": {"message": "No action needed: analysis complete - no issues found"}}`. Messages appear in the workflow conclusion comment or step summary. + +**Always include explicit `noop` instructions in your workflow prompts:** + +```markdown +If no action is needed, you MUST call the `noop` tool with a message explaining why: +{"noop": {"message": "No action needed: [brief explanation]"}} +``` ### Missing Tool Reporting (`missing-tool:`)