Agent skill · Security

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).

agentic-communitygithub.com/agentic-communityGitHub ↗
claude-codeApache-2.0
Install
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.

Facts
Files in the skill folder: 10
SKILL.md size: 11 KB
Bundled scripts: none
Version: 1.1
Declared author: mcp-gateway-registry
Path: .claude/skills/pr-review/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 845
Language: Python

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

From the SKILL.md

# 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/

What's inside
Steps it walks through
  1. Input
  2. Output
  3. Workflow
  4. Step 1: Parse PR URL and Fetch PR Details
  5. Step 2: Determine Relevant Personas
  6. Step 2.5: Detect New or Modified Configuration Parameters (CRITICAL)
  7. Step 3: Run Tests and Quality Checks
  8. Step 4: Create Review Folder
  9. Step 5: Conduct Multi-Persona Review
  10. Step 6: Write Comprehensive Review (review.md)
  11. Step 7: Present Review Summary
  12. Review Principles
  13. From CLAUDE.md
  14. Severity Levels
Ships with 9 files
  • personas/ai-agent-developer.md
  • personas/backend-developer.md
  • personas/chief-architect.md
  • personas/devops-engineer.md
  • personas/frontend-developer.md
  • personas/merge-specialist.md
  • personas/security-engineer.md
  • personas/security-patterns.md
  • personas/sre-engineer.md
Commands it runs
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}
More from mcp-gateway-registry
All skills →
About this skill
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.

Keep going