Install any skill in seconds. Free to start, no credit card required.
Get Started Free →oliver-kriska/pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve.
Passed 16 of 19 test cases with the skill, and 12 of 19 without it.
and 2 more in the full report
5 fixed13 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
After applying code fixes for review comments in an Elixir project on PR #77, what verification command should be run locally before showing the final rollup summary?
| Checked | Without skill | With skill |
|---|---|---|
| Runs mix compile --warnings-as-errors. | Passed | Passed |
| Runs mix test scoped to changed files. | Missed | Passed |
The instructions your model reads when the skill loads.
Close the review loop: fetch unresolved threads → fix → reply → resolve.
GitHub's isResolved is the state — re-runs are idempotent, handled
threads drop out automatically.
/phx:pr-review 42 # Triage unresolved threads on PR #42
/phx:pr-review 42 --fix # Triage + apply approved code fixes
/phx:pr-review https://... # Full URL also works (repo parsed from URL)
/phx:pr-review 42 --bots-only # Triage only CI bot threads (Copilot, Codex...)
/phx:pr-review 42 --no-resolve # Reply but leave threads open
gh pr view "$PR" --json number,title,state,baseRefName,headRefName,url,author
(accepts number or URL; URL also yields owner/repo). Then fetch ALL review
threads with thread IDs + resolved status — REST alone cannot do this:
cat > /tmp/review_threads.graphql <<'GQL'
query($owner:String!, $repo:String!, $pr:Int!, $cursor:String) {
repository(owner:$owner, name:$repo) {
pullRequest(number:$pr) {
reviewThreads(first:50, after:$cursor) {
pageInfo { hasNextPage endCursor }
nodes {
id isResolved isOutdated path line originalLine
comments(first:20) { nodes {
databaseId body createdAt
author { login __typename } } }
}
}
}
}
}
GQL
test cases passed, vs 12 / 19 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.