cran-extrachecks

Identify and fix ad-hoc CRAN submission issues in R packages.

466|38|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/posit-dev/skills --skill cran-extrachecks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cran-extrachecks
Source: https://github.com/posit-dev/skills/tree/main/r-lib/cran-extrachecks
Command: npx skills add https://github.com/posit-dev/skills --skill cran-extrachecks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The CRAN Extra Checks Skill helps package developers ensure compliance with ad-hoc CRAN submission requirements that are not covered by standard devtools checks, reducing back-and-forth with CRAN reviewers.

Core Features & Use Cases

  • Systematically verify documentation, DESCRIPTION fields, URLs, and licensing to align with CRAN expectations.
  • Generate actionable remediation steps for issues raised by CRAN reviewers and automate common preparation tasks like News, cran-comments, and README checks.
  • Use case: A first-time CRAN submitter can run this skill to identify and fix issues before submitting, saving time and avoiding delays.

Quick Start

Run the CRAN Extra Checks workflow on your package repository to identify missing documentation, URL issues, and packaging standards.

Frequently Asked Questions about cran-extrachecks

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

FAQPage Schema
How do I check my R package for CRAN submission issues before submitting?

To check your R package for CRAN submission issues, run a pre-check workflow that verifies documentation, DESCRIPTION fields, URLs, and licensing to identify ad-hoc compliance gaps not covered by standard devtools checks.

What CRAN documentation files do I need to prepare for my first R package submission?

For CRAN submission, you need to prepare and validate documentation files including NEWS.md, cran-comments.md, and README, ensuring they meet packaging standards and contain required compliance information.

How do I fix CRAN reviewer feedback about invalid URLs in my R package?

To fix CRAN reviewer feedback about invalid URLs, run URL validation checks on your package repository to identify broken links and receive actionable remediation steps for correcting them.

Does devtools automatically check license year alignment for CRAN submissions?

Standard devtools checks do not verify license year alignment, so you need an extra checks workflow to enforce license year consistency and deliver actionable remediation steps before CRAN submission.

Why does my R package keep getting rejected by CRAN despite passing devtools checks?

Your R package keeps getting rejected by CRAN because standard devtools checks do not cover ad-hoc requirements like NEWS.md, cran-comments.md validity, and license year alignment, which require additional pre-checks to resolve.