pr-review
Review a GitHub pull request using multiple expert personas. Takes a PR URL as input, analyzes the changes, and generates comprehensive review feedback from different perspectives (Merge Specialist, Frontend, Backend, Security, DevOps, AI/Agent, SRE, Chief Architect).
npx skills add agentic-community/mcp-gateway-registry --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 Skill Use this skill to review GitHub pull requests comprehensively using multiple expert personas. Each persona brings specialized knowledge to identify issues from different perspectives. ## Input The skill takes a GitHub PR URL as input: - Format: `https://github.com/{owner}/{repo}/pull/{number}` - Example: `https://github.com/agentic-community/mcp-gateway-registry/pull/123` ## Output Creates review documentation in `.scratchpad/pr-{pr-number}/` containing: - `review.md` - Comprehensive review from all personas ## Workflow ### Step 1: Parse PR URL and Fetch PR Details 1. Extract the PR number from the URL 2. Use `gh pr view {number}` to get PR details 3. Use `gh pr diff {number}` to get the changes 4. Identify which files are changed and their types (frontend, backend, etc.) ### Step 2: Determine Relevant Personas Based on the files changed, determine which personas should review: | Changed Files | Personas to Engage | |---------------|-------------------| | `/frontend/**` | Merge Specialist, Frontend Developer, Chief Architect | | `/registry/**` | Merge Specialist, Backend Developer, Security Engineer, SRE, Chief Architect | | `/registry/core/config.py`, `/registry/
- Input
- Output
- Workflow
- Step 1: Parse PR URL and Fetch PR Details
- Step 2: Determine Relevant Personas
- Step 2.5: Detect New or Modified Configuration Parameters (CRITICAL)
- Step 3: Run Tests and Quality Checks
- Step 4: Create Review Folder
- Step 5: Conduct Multi-Persona Review
- Step 6: Write Comprehensive Review (review.md)
- Step 7: Present Review Summary
- Review Principles
- From CLAUDE.md
- Severity Levels
Any diff that touches one of the canonical parameter-carrying files triggers this check
gh pr diff {pr-number} --name-only | grep -E \
For each new parameter name, confirm the reference file mentions it
for PARAM in $(gh pr diff {pr-number} | grep -E '^\+[A-Z_]{3,}=' | sed 's/^+//;s/=.*//' | sort -u); do
if ! grep -q "$PARAM" docs/unified-parameter-reference.md; then
echo "MISSING from unified-parameter-reference.md: $PARAM"
fi
done
Checkout the PR
gh pr checkout {pr-number}What does the pr-review skill do?
Review a GitHub pull request using multiple expert personas. Takes a PR URL as input, analyzes the changes, and generates comprehensive review feedback from different perspectives (Merge Specialist, Frontend, Backend, Security, DevOps, AI/Agent, SRE, Chief Architect).
How do I install it?
Run `npx skills add agentic-community/mcp-gateway-registry --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 agentic-community/mcp-gateway-registry, a repository with 845 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.
