Repository navigation
[prompt-clustering] Prompt Clustering Analysis - 2026-10-28 #72633
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Copilot Agent Prompt Clustering Analysis. A newer discussion is available at Discussion #72919. |
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-09-28 to 2026-10-27)
Total Tasks Analyzed: 605
Clusters Identified: 7
Overall Success Rate: 84.0% (508 merged / 96 closed / 1 open)
Full Analysis Report
General Insights
Methodology note: clustering used TF-IDF (1-2 grams, 300 features, min document frequency 2) + K-means over cleaned PR title/body text, with k selected by silhouette score across k=3–8 (best: k=7, silhouette 0.054 — a fairly flat, mixed-topic score consistent with this repo's prompts sharing a lot of common vocabulary across task types). Full PR data (comments, reviews, commits, file-change counts) was available in cache for all 605 PRs in the window, so per-cluster engagement stats below reflect complete coverage, not a sample. No workflow-run turn/duration/cost data is included — see Limitations.
Cluster Analysis
Cluster 1: Agent/Workflow Orchestration & GitHub Integration
Cluster 2: Model Routing (Copilot/Claude/Pi)
Cluster 3: Safe-Output Failure Handling & Diagnostics
Cluster 4: Ledger/Memory & Test Coverage Fixes
Cluster 5: Dependency & Image Version Pinning
Cluster 6: PR Sous Chef Bot-Driven Fixes
Cluster 7: Work Queue / Worker System
Success Rate by Cluster
Full Data Table
All 605 analyzed PRs (click to expand)
Showing up to 15 representative PRs per cluster (605 total analyzed; full list cached at
/tmp/gh-aw/cache-memory/prompt-clustering/).runtimes.nodeaction override in threat-detection and evals...add-labels.maxabove 10 for per-call label limitgh aw envKey Findings
Lowest-Merge Cluster Root Cause
Not applicable this run. The lowest-performing cluster (C4: Ledger/Memory & Test Coverage Fixes, 81.7% merged) is only 2.3 points below the 84.0% overall rate — well short of the 10-point gap threshold that triggers a root-cause drill-down, regardless of its size (71 PRs, above the 15-PR size floor). No cluster in this run meets both outlier criteria (size ≥ 15 and gap ≥ 10 points), so Phase 4.5's blocker-classification step was not run. This methodology will automatically re-engage the next time a qualifying outlier appears.
Recommendations
Limitations
gh-aw's own workflow-run logs (via theagenticworkflows logstool) track runs of this repository's own agentic workflows under thecopilotengine, which do not correspond 1:1 to the Copilot coding-agent PRs being clustered here — this was established as a dead end in the 2026-10-26 run and was not re-attempted this cycle./tmp/gh-aw/cache-memory/prompt-clustering/full-pr-table-2026-10-28.jsonfor future runs.Generated by Prompt Clustering Analysis (Run: §40666371572)
References:
All reactions