[prompt-clustering] Copilot Agent Prompt Clustering — 2026-07-05 (1,000 PRs, 81.1% merge rate) #43529
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by Copilot Agent Prompt Clustering Analysis. A newer discussion is available at Discussion #43773. |
Beta Was this translation helpful? Give feedback.
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-06-13 → 2026-07-05 (rolling 30-day window)
Tasks analyzed: 1,000 Copilot-agent PRs (997
copilot-swe-agent, 3github-actions)Clusters identified: 10 (K-means over TF-IDF of title+body, k chosen by silhouette; sil = 0.048)
Overall merge rate: 81.1% (799 merged / 186 closed / 15 open) — up +1.0pp from 80.1% on 2026-07-03
The single strongest quality signal remains WIP PRs: 34 PRs opened as
[WIP]merge at only 35.3% vs 81.1% overall. That's up sharply from 24.2% two days ago, but WIP tasks are still ~2.3× more likely to be abandoned than normal ones.Full analysis report
Key findings
Meta / prompt-engineering work is the weakest cluster. "guidance / report / prompt" (126 PRs, 12.6% of volume) merges at just 72% and carries 7 of the 34 WIP flags. These are workflow-authoring tasks — refactoring shared prompt bundles, tweaking report formatting, rotating cache-memory. Much of it is exploratory and gets closed (e.g. [WIP] Refactor to create shared/guard-otlp.md bundle for workflows #42983, [WIP] Refactor to create shared/serena-otlp.md bundle for workflows #42944 shared-bundle refactors; [WIP] Expand personas and add systematic cache-memory rotation #42090 persona expansion — all WIP/closed).
Mechanical / dependency work is nearly flawless. "smoke claude / domains / claude" (45 PRs) merges at 98% — version bumps, firewall/smoke-domain config, and MCP-container wiring. Long bodies (avg 3,554 chars, mostly smoke-test output) but low ambiguity. Similarly, "rule / cases / false" ESLint/analyzer rules (46 PRs) merge at 91%.
The CI-fixer cluster is a WIP factory. The smallest cluster, "actions / github actions / job" (16 PRs), is 15/16 WIP with the shortest bodies in the dataset (avg 412 chars — auto-generated "Fix failing GitHub Actions job for X" titles). It still lands at 75% merge, so the pattern works, but nearly every one starts as a draft/WIP retry loop.
Volume is concentrated in config & error-fixing. The two largest clusters — "schema / added / workflows" (239 PRs, 75%) and "error / failure / runs" (178 PRs, 81%) — together are 42% of all tasks. Schema/config work under-performs the mean (75%), suggesting spec/validation changes are where the agent most often gets a rejection.
Cluster analysis
Representative PRs per cluster
replace-labelsafe-outputs type (experimental) #40423 Addreplace-labelsafe-outputs type · Implementmcp-scripts.dependenciesend-to-end with runtime-manager install flow and pinned release-tag validation #39739mcp-scripts.dependenciesend-to-end · [WIP] Fix safe outputs MCP container path for consumer repos #39695 [WIP/closed] MCP container path for consumer reposskilletskill-routed PR reviewer workflow #40399skilletskill-routed PR reviewer · fix: prevent stdout/stderr interleaving in mcp_cli_bridge for large outputs #40037 fix stdout/stderr interleaving in mcp_cli_bridgedeferinloopanalyzer · ctxbackground: fix false negative and unsafe autofix for closures #41187 ctxbackground false-negative fixTrend vs previous run (2026-07-03)
Merge rate has held in a tight 79–82% band across the whole recorded history (since 2026-06-17), so day-to-day moves are noise rather than regime change. The WIP merge-rate jump is the only material shift.
Methodology & limitations
min_df=3,max_df=0.55, sublinear, 800 features) over cleaned title+body; code fences, URLs, and#refsstripped.pr-full-data/cache is stale (PRs #30k, dated May 24) and does not intersect the current window (#38k–43k), so turn counts, duration, and cost could not be joined. Analysis is prompt-text + outcome only — consistent with prior runs, which also lacked turn data.Recommendations
[WIP]as a retry smell, not a status. WIP PRs merge at 35% and the CI-fixer cluster is 15/16 WIP. Consider having the agent iterate to green before opening, or auto-converting stale WIP drafts — a lot of the gap is retry churn on failing CI.References: §28737657305
Beta Was this translation helpful? Give feedback.
All reactions