Modern R development skills for Claude Code - tidyverse patterns, rlang metaprogramming, Bayesian inference, performance optimization, and more
Review code for security, quality, and best practices. Use after writing code and before committing.
Create an implementation plan before writing code. Use for new features, architectural changes, or complex refactoring.
Test-driven development workflow for R. Write tests first, then implement. Use for new features, bug fixes, and refactoring.
Run full R verification loop before committing. Checks build, lint, style, test coverage, and code quality.
Test-driven development specialist for R. Enforces test-first development with testthat. Use when writing new features, fixing bugs, or refactoring code.
Expert planning specialist for R projects. Use for feature implementation, architectural changes, or complex refactoring. Automatically activated for planning tasks.
Senior R code review specialist. Use after writing code to review for security, quality, and best practices before committing.
Use this skill for any R question touching brms or the Bayesian multilevel workflow: writing random effects formulas (random intercepts, random slopes, crossed random effects), getting marginal effects on interpretable scales via marginaleffects, setting up lagged or person-centered variables in longitudinal/ESM data, identifying adjustment sets from DAGs with dagitty, or checking model diagnostics. Invoke whenever the user mentions brms by name, asks how to structure a multilevel formula, wants probability-scale effects from a Bayesian model, or needs to prepare time-series data before fitting a multilevel model — regardless of whether they frame it as Bayesian.
R object-oriented programming guide for S7, S3, S4, and vctrs. Use when designing R classes or choosing an OOP system.
Use this skill for R package development questions involving design decisions and best practices: managing dependencies (when to use Imports vs Suggests, avoiding dependency bloat, tidyverse integration), designing user-facing APIs (tidy evaluation, non-standard evaluation, accepting bare column names vs strings), organizing code (internal helpers vs exported functions, file layout), error handling and custom error classes, input validation, testing strategies with testthat, and roxygen2 documentation. Invoke when a user is building or maintaining an R package and asking how to structure, design, or implement something within it — especially architectural trade-offs and R-package-specific conventions.
R performance best practices including profiling, benchmarking, vctrs, and optimization strategies. Use when optimizing R code.
R style guide covering naming conventions, spacing, layout, and function design best practices. Use when writing R code.
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Uses Bash, Write, or Edit tools
Uses Bash, Write, or Edit tools
Version 1.2.3 | Last updated: 2026-02-21
A curated collection of Claude Code configurations for modern R use. These skills, rules, commands, and agents help Claude Code understand R best practices and generate idiomatic, high-quality R code. Additionally the rules and commands help with efficient token usage and enforce constraints, and agents can perform specific tasks. Obviously you can fork and adapt any of these to your case-use.
I use Positron, but if you are a VSCode user there is also a plugin for R language server for code intelligence.
This project uses and builds on the work of:
Sarah Johnson's Modern R Development Guide - Original guide that formed the foundation for the R skills in this repository
Jeremy Allen's Claude Skills Repo - Jeremy's Claude Skills mostly derived from Sarah's guide
Affaan Mustafa's Everything Claude Code - Framework structure, rules, commands, and agents adapted for R development from Affan's Hackathon winning code
Posit's testing-r-packages Skill - testthat Edition 3 patterns, test design principles, and comprehensive expectations reference incorporated into the tdd-workflow skill
As an aside, I use Quarto in my workflow and use Posit's Quarto plugin which you can add with: /plugin marketplace add posit-dev/skills and then /plugin install quarto@posit-dev-skills.
This repository provides Claude Code configurations specifically for R users, combining:
Claude Code uses five official feature types to customise its behaviour for R development, plus a custom convention (Contexts) built on the CLI's --system-prompt flag. Each serves a distinct purpose in the development workflow.
What they are: Markdown documents containing domain knowledge, best practices, and coding patterns that Claude references when writing code. Skills are passive knowledge resources loaded into Claude's context when relevant.
When to use: Claude automatically activates skills based on the code you're working on. For example, when you're writing tidyverse code, the tidyverse-patterns skill provides guidance on modern pipes, joins, and grouping.
How they work: Skills live in .claude/skills/ and contain detailed guidance, anti-patterns to avoid, and code examples. Claude consults these when making implementation decisions.
How to use:
# Skills are automatically activated - no manual invocation needed
# You can also explicitly request skill usage in your prompts:
"Write a function using tidyverse-patterns to summarize data by group"
What they are: User-invocable shortcuts (prefixed with /) that trigger specific workflows or behaviours. Commands are active - you call them explicitly to perform actions.
When to use: Use commands when you want Claude to follow a specific workflow, such as planning before implementation (/plan) or conducting a code review (/code-review).
How they work: Commands are defined in the commands/ directory and can trigger agents, enforce specific behaviours, or structure Claude's responses in particular ways.
How to use:
# In your Claude Code conversation:
/plan Add bootstrap confidence intervals to model output
npx claudepluginhub gidonfrischkorn/claude-code-r-skillsEvidence-gated AI coding workflow: scan → analyze → plan → TDD → execute → fix → verify → review, powered by Codebase Memory MCP >= 0.9.0 with optional Serena LSP intelligence. Includes blast-radius planning, test/cycle gates, independent review, and Windows Git Bash hook auto-resolution.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Consult multiple AI coding agents (Gemini, OpenAI, Grok, Perplexity, plus codex, antigravity, and grok CLIs when installed) to get diverse perspectives on coding problems
Production-grade engineering skills for AI coding agents — covering the full software development lifecycle from spec to ship.
Feature development with code-architect/explorer/reviewer agents, CLAUDE.md audit and session learnings, and Agent Skills creation with eval benchmarking from Anthropic.
Lazy senior dev mode. Forces the simplest, shortest solution that actually works: YAGNI, stdlib first, no unrequested abstractions.