Repository navigation
[prompt-clustering] Prompt Clustering Analysis - 2026-10-30 #73163
Closed
Replies: 1 comment
|
This discussion was automatically closed because it expired on 2026-10-31T10:06:28.607Z.
|
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 (as of 2026-10-30)
Total Tasks Analyzed: 595 copilot-agent PRs
Clusters Identified: 7
Overall Success Rate: 76.6% (merged / all analyzed PRs, including 52 still-open); 84.0% among the 543 PRs with a final decision (merged vs. closed) — consistent with the prior cycle's 84.0%
Full Analysis Report
General Insights
gh-aw logs/turn-count data was not available in this run's environment, so iteration complexity is approximated using comment/review/commit counts per PR instead of agent turn counts (see Edge Cases note at end of report).Cluster Analysis
Cluster 1: Agentic Workflow & Safe-Output Fixes
Cluster 2: Test Coverage & Regression Fixes
Cluster 3: Model Routing & Engine Support
Cluster 4: Dependency / Version Pin Bumps
Cluster 5: Work Queue & Dispatch
Cluster 6: Sous Chef Automated PRs
Cluster 7: Detection & Regression Jobs
Success Rate by Cluster
Trend vs. Previous Cycle (2026-10-28)
The two largest swings (workflow/safe-output and version/pins) both coincide with a higher share of currently-open (undecided) PRs in this snapshot than in the prior cycle, which mechanically depresses the raw "merged / all" rate. This is noted as a measurement caveat, not necessarily a quality regression — worth re-checking once those PRs resolve in the next cycle.
Key Findings
Lowest-Merge Cluster Note (Version/Pin Bumps)
CHANGES_REQUESTEDreview status with resolved threads before closing (review friction), one had no review activity at all (likely superseded/stale), and one was an active multi-commit PR with heavy bot-driven comment activity. No single dominant blocker pattern emerged from this small sample.Recommendations
Full Data Table
Sample of analyzed PRs by cluster (up to 12 per cluster; 595 total analyzed)
Edge Cases & Limitations
gh-aw logs(turn counts, duration, cost) was not reachable from this sandbox environment, so per-task iteration complexity is approximated via comment/review/commit counts on each PR rather than agent turn counts.References:
All reactions