[prompt-clustering] Prompt Clustering Analysis - 2026-08-04 #50233
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Copilot Agent Prompt Clustering Analysis. A newer discussion is available at Discussion #50534. |
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-16 → 2026-08-04 (~19 days, most recent 1,000 copilot-authored PRs)
Total Tasks Analyzed: 1,000
Clusters Identified: 9
Overall Merge Rate: 75.7% (757 merged, 237 closed unmerged, 6 still open)
Task prompts were reconstructed from each PR's title + body (the agent's own running task description, truncated before the
START COPILOT CODING AGENTmarker), cleaned of code fences/URLs/issue refs, then clustered with TF‐IDF (unigrams+bigrams, 300 features) + K‐means (k selected via elbow method, capped 5–9). Noaw_info.json/ turn-count data was available in this run (thegh-awCLI is not installed in this sandbox), so "iteration effort" below is approximated with comment/review/commit counts rather than agent turn counts — see Limitations.Full Analysis Report
General Insights
eslint-factory), one-off bug fixes, and new test coverage. Its size and generic top terms (test,fix,add,error) reflect that this repo's agent workload is dominated by small, mechanical fix/test tasks rather than any single coherent feature.Cluster Analysis
Cluster 1: General bug fixes & test coverage
eslint-factorylinter-rule fixes, one-off bug patches, and added test coverage. High volume, above-average success — these are well-scoped, mechanical tasks the agent handles reliably.--rootlessflag for install script), Use native go-gh REST clients for release and ref lookups #47547 (native go-gh REST clients)Cluster 2: Workflow & evals maintenance
Cluster 3: Engine/model/auth bug fixes
model: auto/model: noneto bypass model pinning on automatic-selection plans #46556 (supportmodel: auto/none), fix: escape MCP env secrets with \${VAR} for non-Copilot engines to prevent heredoc JSON corruption #49450 (escape MCP env secrets)Cluster 4: Dependency & container pinning
Cluster 5: Feature/refactor grab-bag
Cluster 6: Large-function refactors & docs
largefunc/funcparamslinters, plus docs-site restructuring. Large mechanical diffs plus below-average merge rate hint that these are more likely to be redirected, split, or superseded by a cleaner follow-up PR.Cluster 7: Safe Outputs & sandbox hardening
safe-outputsbridge and sandbox/credential isolation — a security-sensitive area with above-average review depth.GH_AW_INPUT_*to MCP container)Cluster 8: Workshop UI/UX
/workshop/hackathon-blue-bat-18/) #46579 (route workshop to org-scoped path)Cluster 9: CI job auto-fix (WIP triage)
[WIP] Fix failing GitHub Actions job X" tasks from a CI-failure-triage workflow. Very low review overhead — small, targeted, mostly rubber-stamped.Success Rate by Cluster
Sample Data Table
3 highest-discussion PRs per cluster (27 of 1,000 shown)
Key Findings
Recommendations
eslint-factorybug-fix tasks) may raise the merge rate.gh-aw logsturn/cost data included. This run had no workflow-run correlation (see Limitations) — turn counts and cost per cluster would sharpen the "iteration effort" story beyond the comment/review proxy used here.Limitations
gh-awCLI was not available in this sandbox, so Phase 2 (turns, duration, cost per PR) could not be completed. All "effort" metrics above are PR-level proxies (comments, reviews, commits, files changed), not agent iteration counts.START COPILOT CODING AGENTmarker, the full body (an agent-authored changelog) was used as a proxy.Generated by Prompt Clustering Analysis (Run: 30901094702)
All reactions