[prompt-analysis] Copilot PR Prompt Analysis - 2026-08-21 #54616
Closed
Replies: 1 comment
|
This discussion was automatically closed because it expired on 2026-08-22T20:50:34.718Z.
|
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.
🤖 Copilot PR Prompt Pattern Analysis - 2026-08-21
Summary
Analysis Period: Last 30 days
Total PRs: 1000 | Merged: 767 (76.7%) | Closed: 211 (21.1%) | Open: 22 (2.2%)
Completed merge rate (merged / (merged+closed)): 78.4%
Prompt Categories and Success Rates
(Categorized by keyword matching on title + body; bug-fix is the largest and most common category.)
Prompt Analysis
✅ Successful Prompt Patterns
Common characteristics in merged PRs:
workflow,github,changes,added,existing,lock,coverage,agent,yaml,pathpkg/colorwriter,purity_scan.go) rather than broad goalsExample successful prompts:
❌ Unsuccessful Prompt Patterns
Common characteristics in closed PRs:
workflow,github,actions,generated,copilot,engine,repo,keep,call[WIP]-tagged or exploratory titles signaling unfinished/uncertain scopeExample unsuccessful prompts:
Key Insights
[WIP]labeling appears disproportionately in closed PRs, indicating unfinished or exploratory asks are more likely to be abandoned/closed.Recommendations
pkg/colorwriter/README.md) — this correlates with merged outcomes.[WIP]/ exploratory — these have a much higher closure rate; only submit prompts once scope is fully defined.Historical Trends
Trend: Success rate has declined gradually from ~82% (early July) to 78.4% (current), a ~3.4pp drop over the observed period. Bug fixes remain the dominant category by volume, though refactoring and feature prompts now show higher success rates than bug fixes — suggesting bug-fix prompts may benefit from tighter, more specific framing (error messages, reproduction steps, target files) to recover success rate.
Generated by Copilot PR Prompt Analysis (Run: 32525062830)
All reactions