메뉴
Review R scripts for code quality, reproducibility, and domain correctness. Checks set.seed, paths, structure, figure quality, and conventions. Use when the user asks to review R code or check scripts in scripts/R or Figures.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Read MEMORY.md at session start and apply [LEARN:tag] corrections; when the user corrects you, append [LEARN:category] wrong → right to MEMORY.md. Use when starting work on this project or when the user gives a correction to remember.
Run holistic pedagogical review on lecture slides. Checks 13 patterns: narrative arc, notation density, pacing, motivation before formalism, worked examples, fragment reveals, box hierarchy. Use when the user asks for pedagogy or teaching-quality review of slides.
Run proofreading on lecture files (.tex or .qmd). Checks grammar, typos, overflow, consistency, and academic quality. Produces a report only; does not edit files. Use when the user asks to proofread slides or check grammar/typos in lecture content.
Adversarial QA comparing Quarto slides to Beamer benchmark. Run critic (find issues) then fixer (apply fixes); repeat until approved or max 5 rounds. Use when the user asks to QA Quarto vs Beamer or validate a lecture translation.
Run combined multi-dimensional slide review: visual audit, pedagogy review, and proofreading (and optionally TikZ parity). Use when the user asks for full or comprehensive slide review before a milestone.
Perform visual layout audit of Quarto or Beamer slides. Checks overflow, font consistency, box fatigue, spacing, and layout. Use when the user asks for a visual or layout audit of slides.
| name | review-r |
| description | Review R scripts for code quality, reproducibility, and domain correctness. Checks set.seed, paths, structure, figure quality, and conventions. Use when the user asks to review R code or check scripts in scripts/R or Figures. |
Run the R code review protocol. Produce reports only — do not edit R files.
Identify scripts from the user's message (one file, "LectureN", or "all"). Look in scripts/R/, Figures/*/, and project .R files.
For each script, check (use .claude/rules/r-code-conventions.md if present):
set.seed() at top, relative paths, no absolute paths, dir.create() for outputscat()/print() for status; use message() sparinglySave report to quality_reports/[script_name]_r_review.md. Use severity: Critical / High / Medium / Low.
Do NOT edit R source files. Present summary: issues per script, severity breakdown, top critical issues.