Agent skill · Code Review & Quality

phx-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.'

oliver-kriskagithub.com/oliver-kriskaGitHub ↗
claude-codeMIT
Install
npx skills add oliver-kriska/claude-elixir-phoenix --skill phx-pr-review --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 6 KB
Bundled scripts: none
Path: targets/amp/skills/phx-pr-review/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 515
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# PR Review Response Inspect unresolved pull-request review threads, triage them read-only by default, and apply only explicitly approved fixes. GitHub mutations are never implied. ## Usage ```text phx-pr-review 42 phx-pr-review 42 --fix phx-pr-review https://github.com/owner/repo/pull/42 --bots-only phx-pr-review 42 --no-resolve ``` ## Workflow 1. Resolve the PR number or URL. Prefer a runtime GitHub connector that returns thread IDs and resolved state. Otherwise use this exact `gh` 2.94-compatible fallback (requires `command -v gh` and `gh auth status`): ```bash PR_INPUT="${1:?PR number or URL}" if [[ "$PR_INPUT" =~ ^https://github.com/([^/]+)/([^/]+)/pull/([0-9]+) ]]; then OWNER="${BASH_REMATCH[1]}"; REPO="${BASH_REMATCH[2]}"; PR="${BASH_REMATCH[3]}" else OWNER=$(gh repo view --json owner --jq '.owner.login') REPO=$(gh repo view --json name --jq '.name'); PR="$PR_INPUT" fi gh api graphql --paginate -F owner="$OWNER" -F repo="$REPO" -F pr="$PR" -f query='query($owner: String!, $repo: String!, $pr: Int!, $endCursor: String) { repository(owner: $owner, name: $repo) { pullRequest(number: $pr) { reviewThreads(first: 100, after: $endCursor) { nodes { id isResolved isOutdated path line

What's inside
Steps it walks through
  1. Usage
  2. Workflow
  3. Iron Laws
  4. References
Ships with 3 files
  • references/bot-triage.md
  • references/gh-commands.md
  • references/response-patterns.md
Commands it runs
if [[ "$PR_INPUT" =~ ^https://github.com/([^/]+)/([^/]+)/pull/([0-9]+) ]]; then
else
fi
More from claude-elixir-phoenix
All skills →
About this skill
What does the phx-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 phx-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.

Keep going