How do I install the Review R skill?

Run npx skillmds@latest add brycewang-stanford/review-r-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Review R safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Review R?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Review R free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Review R?

brycewang-stanford (@brycewang-stanford) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Review R by brycewang-stanford — Agent Skill

Name: Review R
Rating: 4.666666666666667 (3 reviews)
Author: brycewang-stanford

Review R

Run the R code review protocol on R scripts. Checks code quality, reproducibility, domain correctness, and professional standards. Produces a report without editing files. Make sure to use this skill whenever the user wants their existing R code evaluated or audited — not when they want new analysis written. Triggers include: "review my R script", "check my R code", "is my code replication-ready", "audit this R file", "does this code follow conventions", "will this reproduce", "check my analysis script", "code review", "review-r", or when the user has an existing .R file and wants quality feedback rather than new code.

brycewang-stanford Updated Sep 9, 2026 1k repo stars

File contents

Review R Scripts

Run the comprehensive R code review protocol.

Steps

Identify scripts to review:
- If $ARGUMENTS is a specific .R filename: review that file only
- If $ARGUMENTS is a name pattern (e.g., model_name): glob for matching .R files. If multiple matches, use AskUserQuestion:
  - header: "Scripts"
  - question: "Multiple R scripts match that pattern. Which should I review?"
  - multiSelect: true
  - options: list up to 4 matched files (label: filename, description: path and last modified). User can select multiple.
- If $ARGUMENTS is all: review all R scripts in scripts/R/ and Figures/*/
- If $ARGUMENTS is empty, glob for all .R files. If multiple found, use AskUserQuestion as above.
For each script, launch the r-reviewer agent with instructions to:
- Follow the full protocol in the agent instructions
- Read rules/r-code-conventions.md for current standards
- Save report to quality_reports/[script_name]_r_review.md
After all reviews complete, present a summary:
- Total issues found per script
- Breakdown by severity (Critical / High / Medium / Low)
- Top 3 most critical issues
IMPORTANT: Do NOT edit any R source files. Only produce reports. Fixes are applied after user review.

---name: review-r-2description: Run the R code review protocol on R scripts. Checks code quality, reproducibility, domain correctness, and professional standards. Produces a report without editing files. Make sure to use this skill whenever the user wants their existing R code evaluated or audited — not when they want new analysis written. Triggers include: "review my R script", "check my R code", "is my code replication-ready", "audit this R file", "does this code follow conventions", "will this reproduce", "check my analysis script", "code review", "review-r", or when the user has an existing .R file and wants quality feedback rather than new code.--- # Review R Scripts Run the comprehensive R code review protocol. ## Steps 1. **Identify scripts to review:** - If `$ARGUMENTS` is a specific `.R` filename: review that file only - If `$ARGUMENTS` is a name pattern (e.g., `model_name`): glob for matching `.R` files. If multiple matches, use AskUserQuestion: - header: "Scripts" - question: "Multiple R scripts match that pattern. Which should I review?" - multiSelect: true - options: list up to 4 matched files (label: filename, description: path and last modified). User can select multiple. - If `$ARGUMENTS` is `all`: review all R scripts in `scripts/R/` and `Figures/*/` - If `$ARGUMENTS` is empty, glob for all `.R` files. If multiple found, use AskUserQuestion as above. 2. **For each script, launch the `r-reviewer` agent** with instructions to: - Follow the full protocol in the agent instructions - Read `rules/r-code-conventions.md` for current standards - Save report to `quality_reports/[script_name]_r_review.md` 3. **After all reviews complete**, present a summary: - Total issues found per script - Breakdown by severity (Critical / High / Medium / Low) - Top 3 most critical issues 4. **IMPORTANT: Do NOT edit any R source files.** Only produce reports. Fixes are applied after user review.

Frequently asked questions