pr-review — Claude Code skill: what it does, how to install
Two-phase pull request review for skill repositories, combining automated schema checks with content audits.
npx skills add MiniMax-AI/skills --skill pr-review -a claude-codeWhat pr-review does
The skill handles pull request reviews in two distinct phases: automated validation followed by content evaluation. First, it runs python .claude/skills/pr-review/scripts/validate_skills.py to verify that SKILL.md exists, required YAML fields are present, and no plaintext secrets are committed.
The second phase inspects skill trigger conditions, environment variable usage for API keys, and documentation updates across README.md and README_zh.md. The workflow is tied directly to the MiniMax repository structure, so running it outside this layout will fail during the script execution stage.
What it helps with
- validate SKILL.md structure and YAML frontmatter
- catch hardcoded credentials and secrets before merge
- verify environment variable handling for external APIs
- ensure documentation parity across README and README_zh
Example prompts for the agent
- Review this pull request against repository standards
- Validate the new skill submission with pr-review
- Check this skill PR for compliance
How to install pr-review
1Skills CLI (Vercel)
npx skills add MiniMax-AI/skills --skill pr-review -a claude-code2Manually: put the files in place
~/.claude/skills/pr-review/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/pr-review/
1Skills CLI (Vercel)
npx skills add MiniMax-AI/skills --skill pr-review -a codex2Manually: put the files in place
.agents/skills/pr-review/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add MiniMax-AI/skills --skill pr-review -a cursor2Manually: put the files in place
.cursor/skills/pr-review/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install MiniMax-AI/skills pr-review2Manually: put the files in place
.github/skills/pr-review/SKILL.md1Skills CLI (Vercel)
npx skills add MiniMax-AI/skills --skill pr-review -a gemini-cli2Platform CLI
gemini skills install https://github.com/MiniMax-AI/skills --path .claude/skills/pr-reviewManually: put the files in place
.devin/skills/pr-review/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add MiniMax-AI/skills --skill pr-review -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set17
The whole set →Similar
Questions about pr-review
How to install pr-review in Claude Code?
Run npx skills add MiniMax-AI/skills --skill pr-review -a claude-code in your terminal. This registers the skill under ~/.claude/skills/pr-review/SKILL.md.
What does pr-review do?
It reviews pull requests using a two-phase check: hard automated validation of skill file structure followed by a qualitative content audit.
What are the prerequisites for running pr-review?
You need Python installed locally so the skill can execute .claude/skills/pr-review/scripts/validate_skills.py during phase one.
Source text
SKILL.md · MIT
--- name: pr-review description: > Review pull requests for the MiniMax Skills repository. Use when reviewing PRs, validating new skill submissions, or checking existing skills for compliance. Run the validation script first for hard checks, then apply quality guidelines for content review. Triggers: PR review, pull request, validate skill, check skill. license: MIT metadata: version: "1.0" category: tooling --- # PR Review Skill Review pull requests against repository standards. Two-phase process: automated validation, then manual content review. ## Phase 1: Automated Validation (Hard Rules) Run the validation script to check structural requirements: ```bash python .claude/skills/pr-review/scripts/validate_skills.py ``` The script checks: - `SKILL.md` exists in every skill directory - YAML frontmatter is parseable - Required fields present: `name`, `description` - `name` matches directory name - No hardcoded secrets detected All ERROR-level checks must pass. WARNING-level items (missing `license`, `metadata`) should be flagged but are not blockers. See [references/structure-rules.md](references/structure-rules.md) for the complete hard rules specification. ## Phase 2: Content Review (Soft Guidelines) After automated checks pass, review the PR against quality guidelines: 1. **Skill scope** — Does it overlap with existing skills? Is the boundary clear? 2. **Description quality** — Does the `description` include clear trigger conditions? 3. **File size** — Are reference docs reasonably sized for context window consumption? 4. **API key handling** — If external APIs are used, are credentials read from environment variables? 5. **Script quality** — Do scripts have shebang, requirements.txt, and error handling? 6. **Language** — Are SKILL.md and code written in English? 7. **README sync** — Are `README.md` and `README_zh.md` updated for new skills? See [references/quality-guidelines.md](references/quality-guidelines.md) for soft guidelines details. ## Review Checklist Summary ### Must Pass (Blockers) - [ ] `validate_skills.py` exits with code 0 - [ ] PR title follows conventional commit format - [ ] One PR, one purpose ### Should Pass (Flagged in Review) - [ ] No functional overlap with existing skills - [ ] Description includes trigger conditions - [ ] Files are reasonably sized - [ ] API keys via environment variables - [ ] README tables updated for new skills (Source column set to `Community`)
© MiniMax-AI · MIT · MiniMax-AI/skills