Add buildkite version of pr failure investigation workflow

[strawgate]

using the buildkite mcp server probably

[github-actions]

TL;DR: I recommend adding a new gh-aw workflow (pr-buildkite-detective) by cloning the existing PR CI detective pattern and swapping GitHub Actions log analysis for Buildkite MCP queries with token-backed auth.

Recommendation
Create a new read-only GitHub Agent Workflow dedicated to Buildkite failure investigation (parallel to pr-ci-detective), not by modifying existing CI detective behavior. Reuse the current gh-aw structure (.github/workflows shim + gh-agent-workflows/(name)/{README.md,example.yml}), and add Buildkite MCP server configuration plus a required BUILDKITE_API_TOKEN secret.

Findings

• Existing PR failure-investigation workflow already exists for GitHub Actions logs:
  • .github/workflows/gh-aw-pr-ci-detective.md:1-115
  • gh-agent-workflows/pr-ci-detective/README.md:1-35
  • gh-agent-workflows/pr-ci-detective/example.yml:1-22
• There is no Buildkite variant in gh-aw workflows right now:
  • rg "buildkite" gh-agent-workflows → no matches
  • rg "buildkite" .github/workflows → no matches
• Buildkite investigation logic exists today only in Claude composite actions:
  • claude-workflows/build-failure-buildkite/rwx/action.yml:27-44 (Buildkite inputs)
  • claude-workflows/build-failure-buildkite/rwx/action.yml:105-111 (Buildkite MCP server URL/auth header)
  • claude-workflows/build-failure-buildkite/rwx/action.yml:195-213 (pipeline/build discovery + log/annotation analysis flow)
• Prior related split/workflow design was already discussed and completed:
  • Issue #121 (closed): split into detective/fixer
  • PR #123 (merged): added pr-ci-detective + pr-ci-fixer

Verification

I ran repository checks to verify current coverage and related history:

$ rg -n "buildkite" gh-agent-workflows
No matches found.

$ rg -n "buildkite" .github/workflows
No matches found.

$ ls gh-agent-workflows | grep -i buildkite
# (no output)

I also verified existing artifacts and prior implementation references:

• gh-agent-workflows/pr-ci-detective/README.md:1-35
• .github/workflows/gh-aw-pr-ci-detective.md:1-115
• claude-workflows/build-failure-buildkite/rwx/README.md:1-46
• Issue #121 and PR #123

Detailed Action Plan

1. Add new gh-aw shim workflow

   • Create .github/workflows/gh-aw-pr-buildkite-detective.md using .github/workflows/gh-aw-pr-ci-detective.md:1-115 as template.
   • Keep read-only permissions and add-comment safe output pattern.
   • Add workflow_call secret for Buildkite token (e.g., BUILDKITE_API_TOKEN) alongside COPILOT_GITHUB_TOKEN.

2. Wire Buildkite MCP server

   • Add a workflow-level mcp-servers entry for Buildkite ((mcp.buildkite.com/redacted) similar to how custom MCP servers are declared in .github/workflows/gh-aw-docs-pr-review.md:62-72`.
   • Add network allowlist entry for the Buildkite MCP domain.
   • Use token auth in MCP configuration (pattern informed by claude-workflows/build-failure-buildkite/rwx/action.yml:105-111).

3. Replace investigation instructions

   • In prompt task steps, replace GitHub Actions log download flow with Buildkite flow:
     • discover pipeline
     • locate build by SHA/branch
     • fetch build details
     • inspect failed job logs and annotations
   • Reuse the investigation sequence from claude-workflows/build-failure-buildkite/rwx/action.yml:195-213, adapted to gh-aw tool names.

4. Add installable workflow docs + trigger example

   • Create gh-agent-workflows/pr-buildkite-detective/README.md based on gh-agent-workflows/pr-ci-detective/README.md:1-35.
   • Create gh-agent-workflows/pr-buildkite-detective/example.yml based on gh-agent-workflows/pr-ci-detective/example.yml:1-22, adding required Buildkite secret mapping.

5. Compile and validate

   • Run make compile (per gh-agent-workflows/DEVELOPING.md:125-140) to generate .lock.yml and dogfood trigger copies.
   • Run make lint (or at minimum make lint-workflows) to validate workflow/example YAML (Makefile:126-129, Makefile:146-153, Makefile:178).

6. Document in top-level listings if needed

   • If workflow inventory tables reference available workflows, add the new entry in README.md and gh-agent-workflows/README.md following the pattern from PR #123.

Related Items

Type	Link	Relevance
Issue	#239	Current request
Issue	#121	Established detective/fixer workflow split pattern
PR	#123	Added existing pr-ci-detective + pr-ci-fixer artifacts
File	.github/workflows/gh-aw-pr-ci-detective.md:1-115	Base gh-aw workflow to clone for Buildkite variant
File	gh-agent-workflows/pr-ci-detective/example.yml:1-22	Base install trigger format
File	gh-agent-workflows/pr-ci-detective/README.md:1-35	Base user-facing docs format
File	claude-workflows/build-failure-buildkite/rwx/action.yml:105-111	Existing Buildkite MCP URL/auth setup reference
File	claude-workflows/build-failure-buildkite/rwx/action.yml:195-213	Existing Buildkite investigation sequence reference
File	gh-agent-workflows/DEVELOPING.md:134-140	Canonical “add a new workflow” checklist

---

What is this? | From workflow: Issue Triage Agent

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. for issue #239

[strawgate]

/ai make a pr please

[github-actions]

Implemented and prepared a PR for a new Buildkite variant of PR failure investigation.

What was added

• gh-agent-workflows/pr-buildkite-detective/example.yml
• gh-agent-workflows/pr-buildkite-detective/README.md
• github/workflows/gh-aw-pr-buildkite-detective.md (shim source)
• docs/workflows/gh-agent-workflows.md updated to list the new workflow and required BUILDKITE_API_TOKEN secret

Behavior

• Mirrors PR CI Detective flow, but uses Buildkite MCP (list_pipelines, list_builds, get_build, job log/annotation analysis) and requires BUILDKITE_API_TOKEN.

Validation run

• make compile
• make lint-workflows
• make lint

Note: per workflow guardrails, the shim was added under github/workflows/; a maintainer must relocate it to .github/workflows/ and run compile before release.

---

What is this? | From workflow: Issue Assistant

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. for issue #239