r-lib-cran-extrachecks

Validate R package documentation, licensing, and URLs for CRAN submission.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/nq-rdl/agent-extensions --skill r-lib-cran-extrachecks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: r-lib-cran-extrachecks
Source: https://github.com/nq-rdl/agent-extensions/tree/main/skills/r-lib-cran-extrachecks
Command: npx skills add https://github.com/nq-rdl/agent-extensions --skill r-lib-cran-extrachecks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prepare R packages for CRAN submission by checking for common ad-hoc requirements not caught by devtools::check. Use when: (1) Preparing a package for first CRAN release, (2) Preparing a package update for CRAN resubmission, (3) Reviewing a package to ensure CRAN compliance, (4) Responding to CRAN reviewer feedback.

Core Features & Use Cases

  • Create NEWS.md if missing and run usethis::use_news_md() for CRAN readiness
  • Create cran-comments.md with guidance to address CRAN checks and reviewer notes
  • Review README to ensure installation instructions are CRAN-safe and free of relative links
  • Proofread DESCRIPTION, ensuring Title/Description meet CRAN guidance and fields are proper
  • Verify COPYRIGHT holder and include required licensing and attribution
  • Review bundled files licensing and ensure third-party content is properly documented
  • Run automated URL checks to ensure https URLs and no redirects

Quick Start

Run the CRAN Extra Checks workflow on my R package to identify documentation, licensing, and URL issues and propose concrete fixes.

Frequently Asked Questions about r-lib-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 requirements?

To check an R package for CRAN submission, validate DESCRIPTION, README, and NEWS files against CRAN policies, ensuring proper documentation, secure URLs, and correct licensing to receive remediation guidance.

What CRAN package checks are missing from devtools::check?

CRAN package checks beyond devtools::check include verifying cran-comments.md exists, ensuring README has no relative links, confirming https URLs without redirects, and checking COPYRIGHT holder and third-party licensing.

How do I prepare an R package for CRAN resubmission?

Prepare an R package for CRAN resubmission by reviewing feedback, creating cran-comments.md to address reviewer notes, updating NEWS.md, and verifying DESCRIPTION fields and URL practices meet CRAN guidance.

Why does CRAN reject R packages with redirecting URLs?

CRAN rejects redirecting URLs because policies require secure, non-redirecting https links. Validate all package URLs to ensure they resolve directly and do not redirect, receiving fixes for non-compliant links.

How do I fix CRAN reviewer feedback about missing NEWS.md?

Fix missing NEWS.md feedback by creating the file and running usethis::use_news_md() for CRAN readiness, ensuring your package meets the required file policies for submission and updates.

Can I use this to check R package licensing and COPYRIGHT fields?

Yes, you can check R package licensing by verifying the COPYRIGHT holder, ensuring required licensing and attribution are included, and reviewing bundled files to confirm third-party content is properly documented.