Add shared agentic-workflows component using tools.agentic-workflows

[Claude]

The gh-aw MCP server was previously configured via a shared import file that manually set up mcp-servers: configuration. This approach required explicit setup steps and didn't leverage the built-in tools.agentic-workflows feature.

Changes

• New shared component: .github/workflows/shared/agentic-workflows.md

  • Uses tools.agentic-workflows field instead of manual mcp-servers: configuration
  • Compiler automatically handles gh-aw installation, binary copying to /opt/gh-aw, and MCP server containerization
  • Works identically in dev and release modes without manual configuration

• Test workflow: .github/workflows/test-agentic-workflows-tool.md

  • Validates the new configuration compiles and generates correct MCP setup
  • Demonstrates usage pattern with both agentic-workflows and github tools

Usage

---
tools:
  agentic-workflows:
  github:
    toolsets: [default]
imports:
  - shared/agentic-workflows.md
---

The compiler generates:

• Installation step for gh-aw extension via GitHub CLI
• Binary copied to /opt/gh-aw for containerization
• MCP server configured with stdio transport in Alpine container
• Workspace and temp directory mounts with GITHUB_TOKEN passthrough

All MCP server tools (status, compile, logs, audit, mcp-inspect, add, update, fix) are available with structured JSON output.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/repos/actions/github-script/git/ref/tags/v8
  • Triggering command: /usr/bin/gh gh api /repos/actions/github-script/git/ref/tags/v8 --jq .object.sha (http block)
  • Triggering command: /usr/bin/gh gh api /repos/actions/github-script/git/ref/tags/v8 --jq .object.sha --abbrev-ref HEAD /usr/bin/base64 (http block)
• https://api.github.com/user
  • Triggering command: /usr/bin/gh gh api user --jq .login #; (http block)
  • Triggering command: /usr/bin/gh gh api user --jq .login m/alias m/bash_completion m/install.sh m/nvm-exec m/nvm.sh m/package.json m/rename_test.sh m/te�� /g m/CODE_OF_CONDUCT.md /usr/bin/sed (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

Determine who configure the gh-aw MCP server using ./gh-aw and migrate it to use the tools.agentic-workflows feature. Make it also work in dev mode.

[github-actions]

🔍 PR Triage Results

Category: feature | Risk: medium | Priority: 45/100

Scores Breakdown

• Impact: 30/50 - New MCP server configuration feature using tools.agentic-workflows; Medium-scale changes (3 files, +620 lines); Enhances workflow capabilities
• Urgency: 8/30 - Less than 1 hour old; Draft status; Medium urgency for new feature
• Quality: 7/20 - CI pending; Draft status; Good description with checklist showing progress; Missing final cleanup

📋 Recommended Action: batch_review

This is a well-structured feature PR adding MCP server configuration support. The changes are moderate in scope (620 additions) and follow good development practices with a clear checklist. Once CI passes and draft status is removed, it should be reviewed alongside other MCP/tooling enhancement PRs.

---

Triaged by PR Triage Agent on 2026-02-03T12:19

AI generated by PR Triage Agent