phxpr-review

Solid

Address PR review comments on Elixir/Phoenix code — fetch comments, draft responses, optionally fix code. Use when the user shares a PR URL or mentions reviewer feedback.

Code & Development 437 stars 25 forks Updated today MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
88
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# PR Review Response Fetch PR review comments, categorize them, draft responses, and optionally apply code fixes. ## Usage ``` /phx:pr-review 42 # Address comments on PR #42 /phx:pr-review 42 --fix # Address + apply code fixes /phx:pr-review https://... # Full URL also works ``` ## Arguments `$ARGUMENTS` = PR number (or URL), optionally followed by `--fix`. ## Workflow ### Step 1: Fetch PR Context Run `gh pr view {number} --json title,body,state,baseRefName,headRefName` for PR metadata. Run `gh api repos/{owner}/{repo}/pulls/{number}/comments --paginate` and `gh api repos/{owner}/{repo}/pulls/{number}/reviews --paginate` for all review comments. Run `gh pr diff {number}` for the diff context. Parse the PR number from `$ARGUMENTS`. If a URL, extract the number from it. Detect `--fix` flag. ### Step 2: Categorize Comments Group each comment into one of these categories: | Category | Signal | Action | |----------|--------|--------| | **Code change** | "should be", "change to", "use X instead" | Draft fix + response | | **Question** | "why", "what if", "how does" | Draft explanation | | **Nitpick** | "nit:", style-only, formatting | Quick acknowledgment | | **Praise** | "nice", "good", "LGTM" | No action needed | | **Discussion** | Architecture, trade-offs, alternatives | Draft thoughtful response | ### Step 3: Map to Code Locations For each code-change comment: 1. Find the file and line from the comment's `path` and `position` 2. Read the c...

Details

Author
oliver-kriska
Repository
oliver-kriska/claude-elixir-phoenix
Created
4 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category