pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
npx skills add oliver-kriska/claude-elixir-phoenix --skill pr-review --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# PR Review Response 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. ## Usage ``` /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 ``` ## Step 1: Resolve PR + Fetch Threads `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: ```bash 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 }
- Usage
- Step 1: Resolve PR + Fetch Threads
- Step 2: Triage Table
- Step 3: Per-Thread Loop
- Step 4: Verify
- Step 5: Final Summary
- Iron Laws
- Integration
- Next Steps
- References
cat > /tmp/review_threads.graphql <<'GQL'
gh api graphql --paginate -F owner="$OWNER" -F repo="$REPO" -F pr="$PR" \
gh api --method POST \
gh api graphql -f query='mutation($threadId:ID!){
thread { id isResolved } }}' -F threadId="$THREAD_ID"What does the pr-review skill do?
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
How do I install it?
Run `npx skills add oliver-kriska/claude-elixir-phoenix --skill pr-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From oliver-kriska/claude-elixir-phoenix, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.