cran-audit

Audit R packages against CRAN Repository Policy and generate a structured gap report.

2|1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/queelius/claude-anvil --skill cran-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cran-audit
Source: https://github.com/queelius/claude-anvil/tree/main/pub-pipeline/skills/cran-audit
Command: npx skills add https://github.com/queelius/claude-anvil --skill cran-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the rigorous process of auditing R packages for compliance with CRAN submission policies, preventing common rejections and streamlining the publication workflow.

Core Features & Use Cases

  • CRAN Readiness Audit: Checks package structure, DESCRIPTION metadata, code quality, documentation, and test coverage against CRAN requirements.
  • Gap Reporting: Generates a structured report detailing issues, their severity, and actionable fixes.
  • Dependency Verification: Ensures all package dependencies are available on CRAN.
  • Use Case: Before submitting an R package to CRAN, use this Skill to perform a comprehensive pre-flight check, identify potential problems, and receive guidance on how to resolve them, significantly increasing the chances of a smooth review process.

Quick Start

Use the cran-audit skill to check the R package in the current directory for CRAN submission readiness.

Frequently Asked Questions about cran-audit

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

FAQPage Schema
How do I check if my R package is ready for CRAN submission?

A CRAN readiness audit verifies package structure, DESCRIPTION metadata, documentation, code quality, and test coverage against CRAN Repository Policy, generating a structured gap report with actionable fixes to prevent submission rejections.

What does a CRAN compliance audit check for in an R package?

A CRAN compliance audit verifies package structure, DESCRIPTION metadata, documentation, code quality, test coverage, and dependency availability against CRAN Repository Policy, producing a structured gap report detailing issues and actionable fixes.

How do I fix common R package rejection issues before submitting to CRAN?

Fix common R package rejection issues by running a pre-submission audit that identifies compliance gaps and offers automated fixes for common problems, ensuring package structure, metadata, documentation, and dependencies meet CRAN standards.

Do I need devtools and covr to audit an R package for CRAN readiness?

Yes, auditing R packages for CRAN readiness requires devtools, urlchecker, and covr to verify package structure, check URL validity, validate dependency availability, and measure test coverage against CRAN submission requirements.

Why does CRAN reject R packages with unavailable dependencies?

CRAN rejects R packages with unavailable dependencies because all required packages must be accessible on the CRAN repository. Dependency verification checks ensure all listed packages are available on CRAN before submission to prevent rejection.

Can I automate CRAN policy compliance checks for R package development?

Yes, you can automate CRAN policy compliance checks during R package development by auditing package structure, metadata, and code quality, with automated fixes for common issues to streamline publication workflows and prevent rejections.