smithery/pedrohcgs

review-r

Read-only R code review protocol for `.R` scripts.

Installation

$ npx skills add smithery/pedrohcgs --skill review-r

Summary

  • Read-only R code review protocol for `.R` scripts.
  • Checks code quality, reproducibility, domain correctness, tidyverse idioms, and professional standards; produces a report without editing.
  • Use when user says "review this R script", "check the R code", "audit the analysis code", "code review on the R", or when an R file is touched as part of a paper submission.
  • NOT for running the code — pair with `/audit-reproducibility` for numeric verification.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/pedrohcgs.

npx skills add smithery/pedrohcgs

Browse all from smithery/pedrohcgs

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsRead, Grep, Glob, Write, Agent, Task
Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,558 B
  • docs SUMMARY.md 187 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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 LectureN: review all R scripts matching that lecture - If $ARGUMENTS is all: review all R scripts in scripts/R/ and Figures/*/

  1. For each script, launch the r-reviewer agent with instructions to:

- Follow the full protocol in the agent instructions - Read .claude/rules/r-code-conventions.md for current standards - Save report to qualityreports/[scriptname]rreview.md

  1. After all reviews complete, present a summary:

- Total issues found per script - Breakdown by severity (Critical / High / Medium / Low) - Top 3 most critical issues

  1. IMPORTANT: Do NOT edit any R source files.

Only produce reports. Fixes are applied after user review.