Fetch PR review comments, verify each against real code/docs, fix valid issues, commit and push
SkillScore67Maintained
Automatic
◆Coding pack
Last verified 8/10/2026
What it changes
Passed 12 of 18 test cases with the skill, and 5 of 18 without it.
Without skill29%
With skill67%
Checks it passed that the model alone missed
Formats fixed replies with the short commit SHA.
Resolves the review thread in GitHub using GraphQL.
Uses thread status values such as replied + resolved.
and 16 more in the full report
11 fixed5 passed either way6 still failing2 broke
Pass-rate lift
+38 pp
Tokens
+38%
Agent turns
0%
Response time
-50%
Model gemini-3.6-flashMeasured 8/10/2026v1 · latest is v216 of 24 cases passed with skill · 18 comparable
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/2/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
See it in action
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 11
Prompt
When verifying if a review comment about React hook dependencies or framework API usage is accurate on PR #12, what tool or command should be queried for project context and documentation questions instead of guessing?
What was checked, without and with the skill
Checked
Without skill
With skill
Recommends checking available resources with `btca resources`.
Missed
Passed
Queries library documentation via btca for framework questions before classifying issues.
Missed
Passed
case-04 · gemini-3.6-flash · 8/10/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md121 linessingle file
Triage PR Review Comments
Fetch all review comments on the current PR, verify each finding against real code, fix valid issues, and push.
Phase 1: Gather Comments
Determine the PR number:
Use $ARGUMENTS if provided
Otherwise: gh pr view --json number --jq .number
Fetch ALL comments (reviewers post in multiple places):
gh api --paginate repos/{owner}/{repo}/pulls/{pr}/reviews
gh api --paginate repos/{owner}/{repo}/pulls/{pr}/comments
gh api --paginate repos/{owner}/{repo}/issues/{pr}/comments
Extract unique findings — deduplicate across Copilot, Greptile, and human reviewers. Group by file and line.
Phase 2: Verify Each Finding
For EVERY finding, verify against real code before accepting or rejecting:
Read the actual code at the referenced file:line
Check if the issue still exists — it may already be fixed in a later commit