add-rcpp-integration
About
This skill adds Rcpp or RcppArmadillo integration to an R package to implement high-performance C++ code for performance bottlenecks. It handles the full setup, writing C++ functions, generating RcppExports, and testing compiled code. Use it when profiling confirms an R function is too slow, you need to interface with C/C++ libraries, or algorithms like loops and linear algebra would benefit from compilation.
Quick Install
Claude Code
Recommendednpx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/add-rcpp-integrationCopy and paste this command in Claude Code to install this skill
Documentation
Add Rcpp Integration
Integrate C++ code into R package using Rcpp for performance-critical operations.
When Use
- R function too slow and profiling confirms bottleneck
- Need to interface with existing C/C++ libraries
- Implementing algorithms benefit from compiled code (loops, recursion)
- Adding RcppArmadillo for linear algebra operations
Inputs
- Required: Existing R package
- Required: R function to replace or augment with C++
- Optional: External C++ library to interface with
- Optional: Whether to use RcppArmadillo (default: plain Rcpp)
Steps
Step 1: Set Up Rcpp Infrastructure
usethis::use_rcpp()
This:
- Creates
src/directory - Adds
Rcppto LinkingTo and Imports in DESCRIPTION - Creates
R/packagename-package.Rwith@useDynLiband@importFrom Rcpp sourceCpp - Updates
.gitignorefor compiled files
For RcppArmadillo:
usethis::use_rcpp_armadillo()
Got: src/ directory created. DESCRIPTION updated with Rcpp in LinkingTo and Imports. R/packagename-package.R contains @useDynLib directive.
If fail: usethis::use_rcpp() fails? Manually create src/, add LinkingTo: Rcpp and Imports: Rcpp to DESCRIPTION. Add #' @useDynLib packagename, .registration = TRUE and #' @importFrom Rcpp sourceCpp to package-level documentation file.
Step 2: Write C++ Function
Create src/my_function.cpp:
#include <Rcpp.h>
using namespace Rcpp;
//' Compute cumulative sum efficiently
//'
//' @param x A numeric vector
//' @return A numeric vector of cumulative sums
//' @export
// [[Rcpp::export]]
NumericVector cumsum_cpp(NumericVector x) {
int n = x.size();
NumericVector out(n);
out[0] = x[0];
for (int i = 1; i < n; i++) {
out[i] = out[i - 1] + x[i];
}
return out;
}
For RcppArmadillo:
#include <RcppArmadillo.h>
// [[Rcpp::depends(RcppArmadillo)]]
//' Matrix multiplication using Armadillo
//'
//' @param A A numeric matrix
//' @param B A numeric matrix
//' @return The matrix product A * B
//' @export
// [[Rcpp::export]]
arma::mat mat_mult(const arma::mat& A, const arma::mat& B) {
return A * B;
}
Got: C++ source file exists at src/my_function.cpp with valid // [[Rcpp::export]] annotation and roxygen-style //' documentation comments.
If fail: Verify file uses #include <Rcpp.h> (or <RcppArmadillo.h> for Armadillo). Export annotation on its own line directly above function signature. Return types map to valid Rcpp types.
Step 3: Generate RcppExports
Rcpp::compileAttributes()
devtools::document()
Got: R/RcppExports.R and src/RcppExports.cpp generated automatically.
If fail: Check C++ syntax errors. Ensure // [[Rcpp::export]] tag present above each exported function.
Step 4: Verify Compilation
devtools::load_all()
Got: Package compiles and loads without errors.
If fail: Check compiler output for errors. Common issues:
- Missing system headers: Install development libraries
- Syntax errors: C++ compiler messages point to line
- Missing
Rcpp::dependsattribute for RcppArmadillo
Step 5: Write Tests for Compiled Code
test_that("cumsum_cpp matches base R", {
x <- c(1, 2, 3, 4, 5)
expect_equal(cumsum_cpp(x), cumsum(x))
})
test_that("cumsum_cpp handles edge cases", {
expect_equal(cumsum_cpp(numeric(0)), numeric(0))
expect_equal(cumsum_cpp(c(NA_real_, 1)), c(NA_real_, NA_real_))
})
Got: Tests pass. Confirm C++ function produces identical results to R equivalent. Handles edge cases (empty vectors, NA values) correctly.
If fail: Tests fail on NA handling? Add explicit NA checks in C++ code using NumericVector::is_na(). Tests fail on empty input? Add guard clause for zero-length vectors at top of function.
Step 6: Add Cleanup Script
Create src/Makevars:
PKG_CXXFLAGS = -O2
Create cleanup in package root (for CRAN):
#!/bin/sh
rm -f src/*.o src/*.so src/*.dll
Make executable: chmod +x cleanup
Got: src/Makevars sets compiler flags. cleanup script removes compiled objects. Both files exist at package root level.
If fail: Verify cleanup has execute permissions (chmod +x cleanup). Makevars uses tabs (not spaces) for indentation if adding Makefile-style rules.
Step 7: Update .Rbuildignore
Ensure compiled artifacts handled:
^src/.*\.o$
^src/.*\.so$
^src/.*\.dll$
Got: .Rbuildignore patterns prevent compiled object files from being included in package tarball. Preserves source files and Makevars.
If fail: Run devtools::check() and look for NOTEs about unexpected files in src/. Adjust .Rbuildignore patterns to exclude only .o, .so, .dll files.
Checks
-
devtools::load_all()compiles without warnings - Compiled function produces correct results
- Tests pass for edge cases (NA, empty, large inputs)
-
R CMD checkpasses with no compilation warnings - RcppExports files generated and committed
- Performance improvement confirmed with benchmarks
Pitfalls
- Forgetting
compileAttributes(): Must regenerate RcppExports after changing C++ files - Integer overflow: Use
doubleinstead ofintfor large numeric values - Memory management: Rcpp handles memory automatically for Rcpp types; don't manually
delete - NA handling: C++ doesn't know about R's NA. Check with
Rcpp::NumericVector::is_na() - Platform portability: Avoid platform-specific C++ features. Test on Windows, macOS, Linux.
- Missing
@useDynLib: Package-level doc must include@useDynLib packagename, .registration = TRUE
See Also
create-r-package- package setup before adding Rcppwrite-testthat-tests- testing compiled functionssetup-github-actions-ci- CI must have C++ toolchainsubmit-to-cran- compiled packages need extra CRAN checks
GitHub Repository
Related Skills
content-collections
MetaThis skill provides a production-tested setup for Content Collections, a TypeScript-first tool that transforms Markdown/MDX files into type-safe data collections with Zod validation. Use it when building blogs, documentation sites, or content-heavy Vite + React applications to ensure type safety and automatic content validation. It covers everything from Vite plugin configuration and MDX compilation to deployment optimization and schema validation.
polymarket
MetaThis skill enables developers to build applications with the Polymarket prediction markets platform, including API integration for trading and market data. It also provides real-time data streaming via WebSocket to monitor live trades and market activity. Use it for implementing trading strategies or creating tools that process live market updates.
creating-opencode-plugins
MetaThis skill helps developers create OpenCode plugins that hook into 25+ event types like commands, files, and LSP operations. It provides the plugin structure, event API specifications, and implementation patterns for JavaScript/TypeScript modules. Use it when you need to intercept, monitor, or extend the OpenCode AI assistant's lifecycle with custom event-driven logic.
sglang
MetaSGLang is a high-performance LLM serving framework that specializes in fast, structured generation for JSON, regex, and agentic workflows using its RadixAttention prefix caching. It delivers significantly faster inference, especially for tasks with repeated prefixes, making it ideal for complex, structured outputs and multi-turn conversations. Choose SGLang over alternatives like vLLM when you need constrained decoding or are building applications with extensive prefix sharing.
