[prompt-clustering] Copilot Agent Prompt Clustering — 2026-07-14 #45446
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by Copilot Agent Prompt Clustering Analysis. A newer discussion is available at Discussion #45716. |
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: Last 30 days (2026-06-24 → 2026-07-14)
Total Tasks Analyzed: 1,000 Copilot agent PRs
Clusters Identified: 8 (TF-IDF + K-means, k selected by silhouette)
Overall Merge Rate: 78.3% (783 merged · 210 closed · 7 open)
Median Time-to-Close: ~2.6h · Mean: ~4.6h
Copilot agent work in
gh-awsplits into eight durable themes. Volume is concentrated in CI failure fixes (24%), the safe-outputs subsystem (20%), and workflow authoring/skills (19%). The cleanest, highest-yield work is ESLint-factory rule authoring (88% merge). The single strongest failure predictor is a PR that ships as a[WIP]/[review]draft — those merge at just 26% versus 78% overall.Cluster overview
[WIP]Full cluster analysis, examples & recommendations
Cluster detail
Cluster 1 — CI job & step failure fixes (240 tasks, 24%)
[WIP]count (18), indicating agents frequently open drafts here before the fix stabilizes.[WIP]ARC/DinD path redirections, closed).Cluster 7 — Safe-outputs subsystem (199 tasks, 20%)
safe.directoryhandling, ingestion hardening. Well-scoped and reliably merged, though some hardening tasks run long (safe_outputs: set git safe.directory via process-scoped env vars before bundle branch pinning #41830 merged after 67h).set_issue_typesafe output from GraphQL to single RESTissues.updatecall #41241 (set_issue_typeGraphQL→REST, merged), safe_outputs: set git safe.directory via process-scoped env vars before bundle branch pinning #41830 (git safe.directory env, merged), Harden issue-intent confidence handling in safe-output ingestion #43168 (issue-intent confidence hardening, closed).Cluster 3 — Workflow authoring & skills (190 tasks, 19%)
.mdworkflow bundles, personas, skills. Fast turnaround but lower merge rate — 12[WIP]drafts, several exploratory refactors closed without merge ([WIP] Expand personas and add systematic cache-memory rotation #42090, [WIP] Refactor to create shared/guard-otlp.md bundle for workflows #42983).Cluster 2 — Docs / spec / schema, SPDD (113 tasks, 11%)
Cluster 0 — SousChef / agent orchestration (82 tasks, 8%)
Cluster 5 — ESLint-factory rules (76 tasks, 8%)
Cluster 6 — Versioning & firewall/domains (58 tasks, 6%)
Cluster 4 — Model & sub-agent config (42 tasks, 4%)
Key findings
[WIP]/[review]prefix is the dominant failure signal. The 47 PRs opened as drafts merged at 26% vs 78% overall — a 3× gap. Draft-first is concentrated in CI-fix (18) and workflow-authoring (12) clusters.Recommendations
[WIP]early — especially in the CI-fix cluster where 18 drafts accumulated.Methodology: title+body TF-IDF (1–2 grams, min_df=3), K-means with k chosen by silhouette over k∈[3,8]. Turn-count enrichment was unavailable (workflow logs not present for this window); "avg hours open" is used as the complexity/iteration proxy. Full-data cache (
pr-full-data/) was stale (May, PR ~30k) and excluded in favor of the fresh 1,000-PR summary set.Generated by Prompt Clustering Analysis (Run: 29324781746)
Beta Was this translation helpful? Give feedback.
All reactions