Menü
R code review on existing scripts. Checks quality, reproducibility, domain correctness, professional standards. Produces report without editing files. Use when evaluating or auditing existing R code, not writing new analysis.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Proofread papers and manuscripts. Checks grammar, typos, layout, consistency, writing quality. Produces report without editing files. Use when finding surface-level errors, not substantive academic critique.
End-to-end data analysis in R or Python — exploration through regression to publication-ready tables and figures. Use when running empirical analysis, writing analysis code, or producing output from data.
Start a new research project. Structured interview formalizes the idea; generates research questions with identification strategies and a project spec. Use when developing or documenting a new research idea, not searching literature or data.
Interactive wizard that configures the social-science-research plugin for a new project. Asks about field, institution, journals, datasets, key researchers, R palette; writes answers to references/domain-profile.md and CLAUDE.md. Use first when starting fresh or configuring the plugin.
Create or update a session log capturing decisions, changes, progress. Use to document what was accomplished during a work session.
Verify every quantitative claim in the paper traces to an analysis output file, and no important output was omitted. Use when checking the paper matches the analysis before submission.
| name | review-r |
| description | R code review on existing scripts. Checks quality, reproducibility, domain correctness, professional standards. Produces report without editing files. Use when evaluating or auditing existing R code, not writing new analysis. |
| when_to_use | review R script, check R code, replication-ready, audit R file, follow conventions, will this reproduce, check analysis script, code review, review-r, quality feedback on .R file |
| argument-hint | [filename, 'all', or analysis name pattern] |
| allowed-tools | ["Read","Grep","Glob","Write","Task","AskUserQuestion"] |
Run the comprehensive R code review protocol.
Identify scripts to review:
$ARGUMENTS is a specific .R filename: review that file only$ARGUMENTS is a name pattern (e.g., model_name): glob for matching .R files. If multiple matches, use AskUserQuestion:
$ARGUMENTS is all: review all R scripts in scripts/R/ and Figures/*/$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:
${CLAUDE_PLUGIN_ROOT}/rules/r-code-conventions.md for current standardsquality_reports/[script_name]_r_review.mdAfter all reviews complete, present a summary:
IMPORTANT: Do NOT edit any R source files. Only produce reports. Fixes are applied after user review.