r-package-check

Validate R packages against CRAN standards with automated checks.

Updated Jun 27, 2026
One-click install
npx skills add https://github.com/fredmilhome/laffer_tobacco --skill r-package-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: r-package-check
Source: https://github.com/fredmilhome/laffer_tobacco/tree/main/.claude/skills/r-package-check
Command: npx skills add https://github.com/fredmilhome/laffer_tobacco --skill r-package-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires devtools, roxygen2, testthat, covr, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of ensuring that R packages are ready for release or submission to CRAN by running a series of checks and generating detailed reports.

Core Features & Use Cases

  • Comprehensive Checks: Includes documentation regeneration, test suite execution, R CMD check, and triage of results.
  • CRAN Policy Compliance: Ensures that packages meet CRAN standards before release.
  • Use Case: A researcher can use this Skill to check their R package for CRAN readiness, receiving a report and checklist for submission.

Quick Start

Check the readiness of your R package by running 'r-package-check'.

Frequently Asked Questions about r-package-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my R package for CRAN submission readiness?

To check R package readiness for CRAN, run automated validations including documentation regeneration, test suite execution, and R CMD check to ensure policy compliance. The process generates a detailed report and submission checklist for package maintainers.

What does R CMD check validate for CRAN policy compliance?

R CMD check validates R packages against CRAN standards by verifying documentation, executing test suites, and triaging results. It ensures package maintainers meet submission requirements by identifying policy violations before release.

Do I need devtools and roxygen2 to run automated R package checks?

Yes, devtools and roxygen2 are required to run automated R package checks, along with testthat and covr. These dependencies facilitate documentation regeneration, test execution, and code coverage analysis for CRAN readiness validation.

How do I automate documentation regeneration and testing for an R package?

Automate documentation regeneration and testing by running a comprehensive check sequence using devtools and roxygen2. This workflow regenerates documentation, executes the testthat suite, and runs R CMD check to validate CRAN compliance.

What's the best way to triage R CMD check results before CRAN submission?

The best way to triage R CMD check results is using an automated validation workflow that executes checks, categorizes errors, and generates a detailed report. This provides a submission checklist for researchers to resolve policy violations.