pr-review
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.
What this skill does
# 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`)
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.