[prompt-analysis] Copilot PR Prompt Analysis - 2026-06-08 #37946
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it expired on 2026-06-09T21:28:56.527Z.
|
Beta Was this translation helpful? Give feedback.
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 | Run: §27167547670
Prompt Categories and Success Rates
Prompt Characteristics Analysis
✅ Successful Prompt Patterns
Common characteristics in merged PRs:
add,update,remove,support,create,ensure,parsefix:→ 88% merged,feat:→ 84% mergedExample successful prompts:
PR Fix "Organizations" typo in docs sidebar (2 locations) #37934 (Merged): "Two adjacent sidebar labels in
docs/astro.config.mjsmisspelled 'Organizations'... One entry also had a double space." — specific file, clear problem, tight scope.PR Replace codex-incompatible
gpt-5-minivariant in Daily Cache Strategy Analyzer #37930 (Merged): "Daily Cache Strategy Analyzerwas failing whenever experiment activation selectedgpt-5-mini, because codex cannot run that model and exits with unknown-model/AI-credit errors." — exact error, named component, clear root cause.❌ Unsuccessful Prompt Patterns
Common characteristics in closed PRs:
[WIP]→ only 27% success rate (40/55 closed)Example unsuccessful prompts:
PR [WIP] Fix failing GitHub Actions job 'agent' #37890 (Closed): "Thanks for asking me to work on this... Fix the failing GitHub Actions job 'agent'. Analyze the Actions logs, identify the root cause of the failure..." — generic instruction with no specific failure detail.
PR Detect MaxAI credit-limit failures from firewall API-proxy event logs in conclusion handling #37927 (Closed): Prompt describes the correct problem in detail but the implementation path duplicated existing logic, leading to a superseding PR. Completeness ≠ correctness.
View Length Distribution Detail
Note: The 400+ word bucket has the worst merged-to-closed ratio — extremely long prompts correlate with more complex/risky changes.
Key Insights
[WIP]in the title have a 27% success rate vs the overall 80%. Copilot should complete work before opening a PR, not use it as a draft placeholder.Recommendations
fix:,feat:).fix:prompts succeed at 88%, the highest of any naming convention observed.[WIP]— this signals incomplete work and predicts closure at 73% rate.Historical Trends (Last 7 Days)
Trend: Success rate dipped from the 81% peak on June 2 to 79.1% on June 6–7, with today showing a recovery to 79.9%. The long-run mean appears to be ~80%.
References: §27167547670
Beta Was this translation helpful? Give feedback.
All reactions