[prompt-clustering] Copilot Agent Prompt Clustering — 2026-07-24 (1000 PRs, 5 clusters) #47770
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Copilot Agent Prompt Clustering Analysis. A newer discussion is available at Discussion #47972. |
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
github/gh-aw)scikit-learn/numpystack was unavailable under PyPy, so an equivalent stdlib implementation was used.Headline finding
[WIP]-prefixed PRs merge at 26% vs a 76% baseline — 56 tasks, only 15 merged. These are agent runs that stalled or were abandoned mid-work, and many are repeated retries of the same task (e.g.Fix failing GitHub Actions job js-integration-live-apirecurs 3×;Add robots.txt to docs siterecurs ~5×). This single pattern accounts for the bulk of wasted cycles.Cluster analysis
Representative PRs per cluster
Cluster 2 — Core engineering — compiler / safe-outputs / workflow internals (490 tasks, 76.9% merged)
Cluster 1 — Dependency & version bumps (AWF, firewall, CLI pins) (189 tasks, 81.5% merged)
Cluster 4 — Agent-generated tasks (sous-chef / AIC security & fixes) (139 tasks, 83.5% merged)
Cluster 0 — Docs site & workshop content (137 tasks, 73.7% merged)
/workshop/hackathon-blue-bat-18/) #46579 [MERGED] Route workshop landing to org-scoped path (/workshop/hackathon-blue-bat-18/)Cluster 3 — Auto-generated CI / [WIP] fix attempts (45 tasks, 37.8% merged)
Cross-cuts (from triage labels)
Trend vs previous run (2026-07-23)
Recommendations
[WIP]runs. 74% of[WIP]PRs never merge and many are identical re-attempts. Deduplicate against open/closed[WIP]titles before dispatching, and cap automatic retries of a task that has already failed twice.js-integration-live-apifixes,robots.txt/llms.txtdocs-site edits). Their repeated failure suggests a missing capability or flaky dependency rather than a prompt problem — route these to a human or a purpose-built workflow instead of the general agent.pr-risk/pr-type; invest triage effort in detecting incomplete/stalled runs early.Notes & limitations
pr-full-datais stale (May, PRs fix(deps_security): propagate context.Context through security advisory HTTP call #30577–34390) and does not overlap the current window (Home page: move Public Preview notice into hero with warning callout styling #43081–47730); pulling fresh workflow logs for ~1000 runs was out of scope for one run. Cluster complexity is proxied by body length and outcome.References: §30086219882
All reactions