▸case-01 Can you check the pull request for my current branch and summarize all the review feedback? I need the comments categorized by severity, a prioritized task list of things to fix, and a list of any unresolved questions that require further clarification. | fail→fail | 4,960 | 4,136 | -17% | 1 | 1 | 0% | 879 | 294 | -67% | 0 | 0 | — |
▸case-02 Pull all the discussion and review comments from the open PR associated with this branch. Please organize the feedback into groups based on importance, provide an ordered list of actionable items, and highlight any pending questions that haven't been answered yet. | fail→fail | 8,520 | 3,656 | -57% | 1 | 1 | 0% | 1,355 | 360 | -73% | 0 | 0 | — |
▸case-03 I want a quick digest of the code review feedback on my active pull request. Please break down the comments by impact level, give me a prioritized todo list of required changes, and note any open queries that still need input. | fail→fail | 3,160 | 4,404 | +39% | 1 | 1 | 0% | 526 | 423 | -20% | 0 | 0 | — |
▸case-04 I need to draft a pull request description for my current branch 'feature/checkout-flow' detailing the API changes and schema migrations. Please generate the PR description template with sections for summary, testing steps, and breaking changes. | pass→pass | 10,563 | 6,831 | -35% | 1 | 1 | 0% | 1,825 | 1,318 | -28% | 0 | 0 | — |
▸case-05 Please approve and merge the pull request #142 for the current branch into the main repository branch using squashed commits. | pass→pass | 4,250 | 10,355 | +144% | 1 | 1 | 0% | 837 | 2,053 | +145% | 0 | 0 | — |
▸case-06 I need to reply to a specific inline review comment on PR #108 saying 'Fixed in commit a1b2c3d'. Please submit this review comment response via GitHub CLI or API. | pass→pass | 6,712 | 8,758 | +30% | 1 | 1 | 0% | 1,463 | 1,817 | +24% | 0 | 0 | — |
▸case-07 Check the open pull request associated with my current git branch 'fix/auth-token-leak' and pull all reviewer feedback. I'm worried reviewers left both high-priority security concerns and minor formatting suggestions; break them down by severity and give me a clear task list ordered by urgency. | fail→fail | 7,674 | 9,039 | +18% | 1 | 1 | 0% | 415 | 398 | -4% | 0 | 0 | — |
▸case-08 Our team leaves top-level discussion comments on the PR overview page as well as line-by-line review comments in the files tab. Please extract feedback from both places on my active branch's PR, group them by impact, and outline a prioritized checklist plus any unresolved questions. | fail→fail | 4,034 | 4,147 | +3% | 1 | 1 | 0% | 683 | 276 | -60% | 0 | 0 | — |
▸case-09 I have several reviewers asking questions on my active PR for 'refactor/database-queries' that need my input, alongside actual change requests. Give me a summary grouping the feedback by severity, a prioritized change list, and an explicit section for open reviewer questions. | pass→fail | 10,133 | 5,396 | -47% | 1 | 1 | 0% | 1,670 | 381 | -77% | 0 | 0 | — |
▸case-10 Reviewers added 15 comments on my active PR. Instead of listing them in chronological order, group them by severity and construct a prioritized action plan where critical fixes come before cosmetic suggestions, along with any unanswered questions. | fail→fail | 5,566 | 7,017 | +26% | 1 | 1 | 0% | 1,038 | 563 | -46% | 0 | 0 | — |
▸case-11 Summarize the pull request feedback on branch 'feat/payment-gateway'. Distinguish actionable code changes from non-actionable suggestions or open questions, group them by severity, and prioritize the necessary work. | fail→fail | 6,788 | 4,771 | -30% | 1 | 1 | 0% | 1,213 | 799 | -34% | 0 | 0 | — |
▸case-12 I need a breakdown of feedback on my current branch's PR. Do not ask me to copy and paste the comments into the chat; inspect the active PR directly, group the feedback by severity, prioritize the fix tasks, and note open queries. | fail→fail | 5,189 | 4,967 | -4% | 1 | 1 | 0% | 892 | 434 | -51% | 0 | 0 | — |
▸case-13 Extract the pull request feedback for branch 'fix/retry-exponential-backoff'. Make sure to gather both inline diff comments and general PR conversations, group them into severity levels, list actionable fixes in priority order, and call out questions awaiting resolution. | pass→fail | 13,233 | 5,428 | -59% | 1 | 1 | 0% | 2,378 | 399 | -83% | 0 | 0 | — |
▸case-14 Summarize reviewer notes for my pull request on branch 'ui/dark-mode-toggle'. Present the feedback organized by severity, followed by a prioritized list of updates to make, and any open questions from design or engineering reviewers. | fail→fail | 2,582 | 5,573 | +116% | 1 | 1 | 0% | 452 | 422 | -7% | 0 | 0 | — |
▸case-15 I just pushed updates to PR on branch 'schema/graphql-user-fields'. Pull all discussion threads and review comments, categorize them by severity, give me an ordered list of high-to-low priority tasks, and highlight open questions. | fail→fail | 5,442 | 5,169 | -5% | 1 | 1 | 0% | 907 | 499 | -45% | 0 | 0 | — |
▸case-16 Fetch all PR feedback for my active branch 'devops/helm-chart-update'. I need the comments structured into severity categories, a prioritized task checklist, and any unresolved questions from the platform team. | fail→fail | 5,273 | 4,968 | -6% | 1 | 1 | 0% | 846 | 378 | -55% | 0 | 0 | — |
▸case-17 Summarize feedback on active branch 'perf/rust-lexer-optimization'. Ensure both inline review comments and top-level conversation items are captured, group them by severity and actionability, and provide a prioritized list of tasks plus open questions. | pass→fail | 15,311 | 4,752 | -69% | 1 | 1 | 0% | 2,470 | 329 | -87% | 0 | 0 | — |
▸case-18 Check the PR for current branch 'data/pandas-chunking'. Provide a feedback breakdown grouped by severity, a prioritized step-by-step action plan, and a dedicated list of open questions left by data engineering reviewers. | pass→fail | 18,635 | 4,681 | -75% | 1 | 1 | 0% | 3,087 | 304 | -90% | 0 | 0 | — |
▸case-19 Pull PR feedback for my current iOS branch 'feature/swiftui-navigation-stack'. Summarize comments grouped by severity, give a prioritized todo list for fixes, and highlight open questions needing decisions. | pass→pass | 15,266 | 11,751 | -23% | 1 | 1 | 0% | 2,319 | 1,696 | -27% | 0 | 0 | — |
▸case-20 Fetch reviewer feedback on active branch 'sec/stripe-webhook-signature'. I want comments grouped by severity, a priority-ordered task list, and any unresolved security or design questions listed separately. | pass→fail | 19,114 | 6,581 | -66% | 1 | 1 | 0% | 3,232 | 366 | -89% | 0 | 0 | — |
▸case-21 Extract PR comments for active branch 'migration/nextjs-app-router'. Organize feedback into severity tiers, provide a prioritized set of actionable items, and surface open questions that need product clarification. | pass→fail | 13,962 | 4,672 | -67% | 1 | 1 | 0% | 2,156 | 470 | -78% | 0 | 0 | — |
▸case-22 Analyze review and discussion comments on my current PR for 'backend/grpc-proto-v2'. Categorize feedback by impact severity, output an ordered list of tasks by priority, and present unanswered reviewer questions. | fail→pass | 6,487 | 12,158 | +87% | 1 | 1 | 0% | 1,072 | 2,149 | +100% | 0 | 0 | — |