[detection-analysis] Detection Analysis Report — 2026-09-04

[github-actions[bot]]

Summary

• Window evaluated: last 24 full hours (UTC) — 2026-09-03T23:32:17Z to 2026-09-04T23:32:17Z
• Total runs analyzed: 254 (207 additional run directories in the pre-downloaded log set had no data and were excluded)
• Detection-enabled runs: 254 (100%)
• Regular runs (gh-aw-detection: false): 0 (0%)
• Misconfigured workflows found: 0

Note

No misconfigured workflows were detected in this window. No workflow explicitly disabled the gh-aw-detection feature, and every detection job that ran completed successfully (240 succeeded, 4 skipped alongside a skipped agent job, 10 absent because the run itself never reached that job).

Comparison Chart

Metric	Regular Runs	Detection Runs
Total runs	0	254
Success rate	0.0%	67.32%
Failure count	0	83
Avg tokens/run	0	164,145

(Regular Runs is empty because no workflow in this window explicitly set gh-aw-detection: false.)

Misconfigured Workflows

No misconfigured workflows detected in this window.

View All Run Metrics

Top workflows by run count (full 108-workflow breakdown, all 100% detection-enabled):

Workflow	Total Runs	Success Rate	Avg Tokens
PR Sous Chef	60	96.67%	411,441
Issue Monster	12	8.33%	12,053
Ponytail Reviewer	10	10.0%	15,192
Design Decision Gate 🏗️	9	88.89%	82,985
Matt Pocock Skills Reviewer	9	100.0%	15,725
PR Code Quality Reviewer	9	100.0%	459,368
Test Quality Sentinel	9	100.0%	9,612
Daily Go Test Parallelizer	8	100.0%	221,451
Impeccable Skills Reviewer	8	100.0%	12,690
AI Moderator	7	0.0%	0
Avenger	5	0.0%	0
Contribution Check	4	100.0%	20,084
Auto-Triage Issues	3	66.67%	155,955
Code Scanning Fixer	3	33.33%	13,704
Smoke Issues	3	33.33%	4,609

Remaining ~93 workflows each had 1–2 runs in the window; success rates ranged from 0% to 100% with no detection-related pattern (failures there trace to unrelated workflow logic — e.g. TokenUsage: 0 runs are agent jobs that were skipped/cancelled before execution, not detection failures).

Note: Issue Monster, Ponytail Reviewer, and AI Moderator show low success rates (8–10%, 0%) but this is not a detection misconfiguration — their detection jobs completed successfully; the failures are in the agent job itself and warrant separate investigation outside this report's scope.

View Historical Trend

Detection-run success rate has declined over the last two days (84.69% → 67.32%), while regular runs (opt-out) have shown zero coverage on 3 of the last 4 days — this repo is now running almost entirely with detection enabled by default, which is the intended posture.

Recommendations

1. No gh-aw-detection misconfigurations require action this cycle — the feature is enabled fleet-wide with no failing detection jobs.
2. The 2-day decline in overall success rate (84.69% → 67.32%) is driven by agent-job failures, not detection — worth a separate investigation into Issue Monster, Ponytail Reviewer, and AI Moderator, which are dragging down the aggregate despite detection working correctly.
3. Continue monitoring: since 0 workflows currently opt out of detection, rule "explicit gh-aw-detection: false on a workflow with >3 runs/week" has nothing to flag today, but re-check after any config changes.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• api.anthropic.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "api.anthropic.com"

See Network Configuration for more information.

Generated by 🔎 Detection Analysis Report · claude · agent · 204.8 AIC · ⌖ 8.79 AIC · ⊞ 9K · ◷

• expires on Sep 7, 2026, 3:38 PM UTC-08:00

[github-actions[bot]]

This discussion has been marked as outdated by Detection Analysis Report.

A newer discussion is available at Discussion #58881.