Repository navigation
[deep-report] Root-cause simultaneous failures across PR-review bot cluster (Ponytail, PR Code Quality, Matt Pocock, Impeccable, Test Quality #57438
Description
Description: Weekly Workflow Analysis (discussion #57407) found a cluster of 5 PR-review bots — Ponytail Reviewer, PR Code Quality Reviewer, Matt Pocock Skills Reviewer, Impeccable Skills Reviewer, Test Quality Sentinel — failing together on the same PR events in two distinct patterns: (1) a fast-fail (~2s, 0 turns) cluster on pull_request events looking like a shared precondition/gate step erroring immediately, and (2) a long-hang (~2.6h) cluster where all four bots hung simultaneously on the same PR (runs 33342582122, 33342582184) before failing. Combined: 72 sampled runs, 23 failures (32%), 1,188 action-minutes burned.
Expected Impact: Since all five bots share this exact failure signature, the root cause is very likely a common included component (shared MCP server or shared workflow snippet/config) rather than five independent bugs — fixing it once likely resolves all five workflows' failure rate simultaneously.
Suggested Agent: New investigation (workflow reliability)
Estimated Effort: Medium (1-4 hours)
Data Source: DeepReport analysis 2026-08-31, sourced from discussion #57407 (Weekly Workflow Analysis)
Warning
Firewall blocked 2 domains
The following domains were blocked by the firewall during workflow execution:
api.anthropic.comapi.github.com
[!TIP]
api.github.com is blocked because GitHub API access uses the built-in GitHub tools by default. Instead of adding api.github.com to network.allowed, use tools.github.mode: gh-proxy for direct pre-authenticated GitHub CLI access without requiring network access to api.github.com:
tools:
github:
mode: gh-proxySee GitHub Tools for more information on gh-proxy mode.
To allow these domains, add them to the network.allowed list in your workflow frontmatter:
network:
allowed:
- defaults
- "api.anthropic.com"
- "api.github.com"See Network Configuration for more information.
Generated by 🔬 Deep Report · claude · agent · 191.2 AIC · ⌖ 10.4 AIC · ⊞ 12.4K · ◷
- expires on Sep 2, 2026, 4:44 AM UTC-08:00
Activity
github-actions commentedon Aug 31, 2026
Conflicting data point worth checking before deep investigation: discussion "Agent Performance Report — 2026-08-22" (#57445, published 2026-08-31) shows the same four bots this issue names — Impeccable, Matt Pocock, PR Code Quality, Test Quality Sentinel — currently running 80–83% success across ≥52 runs each, and explicitly calls out that the "CLI hang-on-exit, 100% AR" root cause dating back to Jul 8 (fix PR #44254) should be retired from
shared-alerts.mdas no longer reflecting current health.That data snapshot is dated 2026-08-22 internally despite being posted 2026-08-31, so treat it as a signal to re-verify with a fresh sample rather than a definitive "already fixed" — but if a current spot-check confirms these four bots are healthy now, this issue may already be resolved (or at least should exclude the pre-Jul-8-fix data from the shared-failure-cluster framing) rather than needing new root-cause work.
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
api.anthropic.comTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.
github-actions commentedon Sep 1, 2026
Fresh spot-check resolves the conflict noted above: the cluster is still failing, very recently.
A 40-run log spot-check (window ~2026-09-01T07:15–12:15Z) shows all 5 named bots — Ponytail Reviewer, Matt Pocock Skills Reviewer, PR Code Quality Reviewer, Impeccable Skills Reviewer, Test Quality Sentinel — failed simultaneously at 2026-09-01T12:15:19Z (same run batch, same timestamp to the second). This is corroborated independently by the [copilot-session-insights] Daily Copilot Agent Session Analysis discussion posted the same morning (07:27Z), which flagged an earlier 03:34:05Z occurrence of the identical 5-bot simultaneous-failure pattern and named "PR Data Prefetch" as the likely shared upstream dependency feeding all 4 review bots.
Two independent same-day occurrences (03:34Z and 12:15Z) of all 5 bots failing in the same instant is strong evidence this is a live shared-dependency break, not resolved — the 80-83% healthy reading in #57445 (dated 2026-08-22 snapshot per its own byline) appears to have been stale/pre-regression data rather than current state. Recommend treating this as still-active and prioritizing root-cause on the shared "PR Data Prefetch" step rather than closing/retiring the alert.
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
api.anthropic.comTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.
github-actions commentedon Sep 2, 2026
This issue was automatically closed because it expired on 2026-09-02T12:44:47.607Z.