[prompt-clustering] Prompt Clustering Analysis - 2026-08-12 #52273
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Copilot Agent Prompt Clustering Analysis. A newer discussion is available at Discussion #52476. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary
Analysis Period: 2026-07-28 to 2026-08-12 (last 30 days)
Total Tasks Analyzed: 1,000 copilot-authored PRs (744 merged, 248 closed, 8 open)
Clusters Identified: 4
Overall Merge Rate: 74.4%
Limitation:
gh-aw logswas not available in this run (noaw_info.jsonworkflow-run data), so turn counts, duration, and cost could not be enriched per PR. This analysis relies on PR body/title text, comments, reviews, and file-change stats only.Full Analysis Report
General Insights
Cluster Analysis
Cluster 1: General bug/refactor/test work
pkg/*. Highest volume and highest success rate of any cluster.Cluster 2: Workflow/agent infra & CI stabilization
smoke-copilot-autolock output by skipping dynamicautopricing injection #48516Cluster 3: Container image / CVE remediation⚠️ outlier
actionpinsspec tests for cache keys, fallback auditing, and container digest validation #48497, [WIP] Fix vulnerabilities in ghcr.io/github/gh-aw-firewall/api-proxy #48498, fix: update brace-expansion to 5.0.8 and upgrade Alpine base image to 3.22 #48521, Remove vulnerablegh-aw-firewall/squid:0.27.41pin from embedded container pin catalogs #48534Cluster 4: Docs, AI-crawler policy & misc engine work
robots.txt/llms.txtAI-crawler policy updates, engine-version normalization, and one-off investigations. Success rate tracks the overall average.Success Rate by Cluster
Turn counts and cost are omitted — workflow-run logs were unavailable this run (see limitation above).
Sample PRs per cluster (20 of 1,000 total — full table omitted for length)
smoke-copilot-autolock outputactionpinsspec tests for cache keys, container digest validationgh-aw-firewall/squid:0.27.41pinKey Findings
Lowest-Merge Cluster Root Cause
[WIP]drafts — not CI failures or reviewer rejectiongh-aw-firewall/squid:0.27.41pin from embedded container pin catalogs #48534, Block scan remediation until patched gh-aw-mcpg image is published #49797, Bump gh-aw-mcpg image to v0.4.9 #51770, Bump gh-aw-mcpg to v0.4.9 #51796 (duplicates of Bump gh-aw-mcpg to v0.4.9 and github-mcp-server to v1.9.0 #51828, all closed), [WIP] Fix container image vulnerabilities for ghcr.io/github/gh-aw-mcpg:v0.4.6 #49672, [WIP] Update container image mcp/arxiv-mcp-server for vulnerabilities #49838 (abandoned[WIP]drafts)Of the 35 closed (non-merged) PRs in this cluster:
[WIP]draft[WIP], task apparently too large/blocked to complete in one run (e.g. waiting on an upstream patched image)@copilotresolve the merge conflicts" commentMerged PRs in this cluster average 6.4 comments each; closed PRs average 0.4, and 80% of closed PRs (28/35) have zero comments at all — a strong signal these are being superseded/duplicated rather than substantively reviewed and rejected. This pattern (quick, low-engagement closes) exists dataset-wide too (~51–60% of all closed PRs), but is markedly stronger in this cluster, consistent with recurring daily security-scan workflows independently filing near-identical fixes for the same vulnerability before the first fix merges.
Recommendations
[WIP]drafts that get silently closed — e.g. auto-label and comment with the blocking dependency, then re-trigger once resolved.Generated by Prompt Clustering Analysis (Run: §31585642928)
All reactions