[prompt-analysis] Copilot PR Prompt Analysis - 2026-08-05 #50692
Closed
Replies: 1 comment
|
This discussion was automatically closed because it expired on 2026-08-06T21:04:04.294Z.
|
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-05
Analysis Period: Last 30 days | Total PRs: 1000 | Merged: 746 (74.6%) | Closed: 248 (24.8%) | Open: 6 (0.6%)
Prompt Categories and Success Rates
Categorization is based on the PR title's leading verb (fix/add/refactor/document/test); most PR bodies follow a standard template, so title phrasing is the strongest categorical signal.
Prompt length and keyword analysis
Average prompt length (words, after stripping URLs/badges/code fences):
Closed PRs skew slightly longer than merged ones — verbosity alone isn't the differentiator; content matters more.
Notable keyword signal — CVE/security-advisory PRs: 15 of 248 closed PRs (6%) reference CVE identifiers (dependency/security-tracker bumps), vs. only 1 of 746 merged PRs. These automated security-scan PRs appear to close at a much higher rate than typical feature/bugfix work, likely due to false positives, duplicate advisories, or being superseded by other dependency updates.
Top keywords in merged PR bodies (post stop-word filtering):
engine,fixes,start,suffix,coding,added,changes,details,summary,tests,behavior,coverage,detection,failure,errorTop keywords in closed PR bodies:
issue,fixes,start,suffix,engine,headers,description,comments,section,prompt,image,container✅ Successful Prompt Examples
❌ Unsuccessful Prompt Examples
gh aw prcommand in CLI reference #50577 — Documentgh aw prcommand in CLI reference → Closed. Documentation PRs with narrow, single-file scope sometimes get superseded/rejected in favor of manual doc edits.[WIP]marker and checklist-style body (partially checked) suggest the task was abandoned or superseded by PR Fix intermittent Kiro/Cursor auth by updating Kiro egress allow-list and SECRET_* API key fallback #50565, a cleaner duplicate of the same fix.Key Insights
Recommendations
fix:,feat:) that name the exact component and blast radius.Historical Trends (last 8 days)
Trend: Overall merge rate has held stable in the 75–77% band for the past ~30 days, with Testing consistently the top or near-top category. Today's overall rate (75.1%) is within normal range, though slightly below the 8-day average (~76%).
Generated by Copilot PR Prompt Analysis (Run: 31046460102)
All reactions