Pr review
Security-audited skills for Claude, Codex & Claude Code. One-click install, quality verified.
npx -y skills add aiskillstore/marketplace --skill pr-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
What its author says it does
Copied from the file, not written here
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.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.4 KB, as published. Nobody here has run it
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:
python .claude/skills/pr-review/scripts/validate_skills.py
The script checks:
SKILL.mdexists in every skill directory- YAML frontmatter is parseable
- Required fields present:
name,description namematches 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 for the complete hard rules specification.
Phase 2: Content Review (Soft Guidelines)
After automated checks pass, review the PR against quality guidelines:
- Skill scope — Does it overlap with existing skills? Is the boundary clear?
- Description quality — Does the
descriptioninclude clear trigger conditions? - File size — Are reference docs reasonably sized for context window consumption?
- API key handling — If external APIs are used, are credentials read from environment variables?
- Script quality — Do scripts have shebang, requirements.txt, and error handling?
- Language — Are SKILL.md and code written in English?
- README sync — Are
README.mdandREADME_zh.mdupdated for new skills?
See references/quality-guidelines.md for soft guidelines details.
Review Checklist Summary
Must Pass (Blockers)
-
validate_skills.pyexits 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)