[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73510FVCFCC6D30YZ9HA2KS":3,"skill-same:01M73510FVCFCC6D30YZ9HA2KS":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":38,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":40,"install":41,"resources":53},"01M73510FVCFCC6D30YZ9HA2KS","cran-extrachecks",null,"CRAN submission checklist beyond devtools::check().","Morrison-Lab\u002Fai-config","Morrison-Lab","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F104235520?v=4","01M734G0451S2G35MN4HFQK7XP","Morrison Lab","01M734G059BYFDFQA8YTPDGPMH",4,"MIT","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fcran-extrachecks\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: cran-extrachecks\ndescription: CRAN submission checklist beyond devtools::check().\nuser-invocable: true\nallowed-tools:\n  - Read\n  - Edit\n  - Write\n  - Bash\nmetadata:\n  author: Garrick Aden-Buie (@gadenbuie)\n  version: \"1.0\"\nlicense: MIT\n---\n\n# CRAN Extra Checks\n\nHelp R package developers prepare packages for CRAN submission by systematically checking for common ad-hoc requirements that CRAN reviewers enforce but `devtools::check()` doesn't catch.\n\n## Workflow\n\n1. **Initial Assessment**: Ask user if this is first submission or resubmission\n2. **Run Standard Checklist**: Work through each item systematically (see below)\n3. **Identify Issues**: As you review files, note specific problems\n4. **Propose Fixes**: Suggest specific changes for each issue found\n5. **Implement Changes**: Make edits only when user approves\n6. **Verify**: Confirm all changes are complete\n\n## Standard CRAN Preparation Checklist\n\nWork through these items systematically:\n\n1. **Create NEWS.md**: Run `usethis::use_news_md()` if not already present\n2. **Create cran-comments.md**: Run `usethis::use_cran_comments()` if not already present\n3. **Review README**:\n   - Ensure it includes install instructions that will be valid when the package is accepted to CRAN (usually `install.packages(\"pkgname\")`).\n   - Check that it does not contain relative links.\n     This works on GitHub but will be flagged by CRAN.\n     Use full URLs to package documentation or remove the links.\n   - Does the README clearly explain the package purpose and functionality?\n   - **Important**: If README.Rmd exists, edit ONLY README.Rmd (README.md will be overwritten), then run `devtools::build_readme()` to re-render README.md\n4. **Proofread DESCRIPTION**: Carefully review `Title:` and `Description:` fields (see detailed guidance below)\n5. **Check function documentation**: Verify all exported functions have `@return` and `@examples` (see detailed guidance below)\n6. **Verify copyright holder**: Check that `Authors@R:` includes a copyright holder with role `[cph]`\n7. **Review bundled file licensing**: Check licensing of any included third-party files\n8. **Run URL checks**: Use `urlchecker::url_check()` and fix any issues\n\n## Detailed CRAN Checks\n\n### Documentation Requirements\n\n**Return Value Documentation (Strictly Enforced)**\n\nCRAN now strictly requires `@return` documentation for all exported functions.\nUse the roxygen2 tag `@return` to document what the function returns.\n\n- Required even for functions marked `@keywords internal`\n- Required even if function returns nothing - document as `@return None` or similar\n- Must be present for every exported function\n\nExample:\n```r\n# Missing @return - WILL BE REJECTED\n#' Calculate sum\n#' @export\nmy_sum \u003C- function(x, y) {\n  x + y\n}\n\n# Correct - includes @return\n#' Calculate sum\n#' @param x First number\n#' @param y Second number\n#' @return A numeric value\n#' @export\nmy_sum \u003C- function(x, y) {\n  x + y\n}\n\n# For functions with no return value\n#' Print message\n#' @param msg Message to print\n#' @return None, called for side effects\n#' @export\nprint_msg \u003C- function(msg) {\n  cat(msg, \"\\n\")\n}\n```\n\n**Examples for Exported Functions**\n\nIf your exported function has a meaningful return value, it will almost definitely require an `@examples` section.\nUse the roxygen2 tag `@examples`.\n\n- Required even for functions marked `@keywords internal`\n- Exceptions exist for functions used purely for side effects (e.g., creating directories)\n- Examples must be executable\n\n**Un-exported Functions with Examples**\n\nIf you write roxygen examples for un-exported functions, you must either:\n\n1. Call them with `:::` notation: `pkg:::my_fun()`\n2. Use `@noRd` tag to suppress `.Rd` file creation\n\n**Using `\\dontrun{}` Sparingly**\n\n`\\dontrun{}` should only be used if the example really cannot be executed (e.g., missing additional software, API keys, etc.).\n\n- If showing an error, wrap the call in `try()` instead\n- Consider custom predicates (e.g., `googlesheets4::sheets_has_token()`) with `if ()` blocks\n- Sometimes `interactive()` can be used as the condition\n- Lengthy examples (> 5 sec) can use `\\donttest{}`\n\n**Never Comment Out Code in Examples**\n\n```r\n# BAD - Will be rejected\n#' @examples\n#' # my_function(x)  # Don't do this!\n```\n\nCRAN's guidance: \"Examples\u002Fcode lines in examples should never be commented out.\nIdeally find toy examples that can be regularly executed and checked.\"\n\n**Guarding Examples with Suggested Packages**\n\nUse `@examplesIf` for entire example sections requiring suggested packages:\n\n```r\n#' @examplesIf rlang::is_installed(\"dplyr\")\n#' library(dplyr)\n#' my_data %>% my_function()\n```\n\nFor individual code blocks within examples:\n```r\n#' @examples\n#' if (rlang::is_installed(\"dplyr\")) {\n#'   library(dplyr)\n#'   my_data %>% my_function()\n#' }\n```\n\n### DESCRIPTION Title Field\n\nCRAN enforces strict Title requirements:\n\n**Use Title Case**\n\nCapitalize all words except articles like 'a', 'the'.\nUse `tools::toTitleCase()` to help format.\n\n**Avoid Redundancy**\n\nCommon phrases that get flagged:\n- \"A Toolkit for\" → Remove\n- \"Tools for\" → Remove\n- \"for R\" → Remove\n\nExamples:\n```r\n# BAD\nTitle: A Toolkit for the Construction of Modeling Packages for R\n\n# GOOD\nTitle: Construct Modeling Packages\n\n# BAD\nTitle: Command Argument Parsing for R\n\n# GOOD\nTitle: Command Argument Parsing\n```\n\n**Quote Software\u002FPackage Names**\n\nPut all software and R package names in single quotes:\n\n```r\n# GOOD\nTitle: Interface to 'Tiingo' Stock Price API\n```\n\n**Length Limit**\n\nKeep titles under 65 characters.\n\n### DESCRIPTION Description Field\n\n**Never Start With Forbidden Phrases**\n\nCRAN will reject descriptions starting with:\n- \"This package\"\n- Package name\n- \"Functions for\"\n\n```r\n# BAD\nDescription: This package provides functions for rendering slides.\nDescription: Functions for rendering slides to different formats.\n\n# GOOD\nDescription: Render slides to different formats including HTML and PDF.\n```\n\n**Expand to 3-4 Sentences**\n\nSingle-sentence descriptions are insufficient.\nProvide a broader description of:\n- What the package does\n- Why it may be useful\n- Types of problems it helps solve\n\n```r\n# BAD (too short)\nDescription: Render slides to different formats.\n\n# GOOD\nDescription: Render slides to different formats including HTML and PDF.\n    Supports custom themes and progressive disclosure patterns. Integrates\n    with 'reveal.js' for interactive presentations. Designed for technical\n    presentations and teaching materials.\n```\n\n**Quote Software Names, Not Functions**\n\n```r\n# BAD\nDescription: Uses 'case_when()' to process data.\n\n# GOOD\nDescription: Uses case_when() to process data with 'dplyr'.\n```\n\nSoftware, package, and API names get single quotes (including 'R').\nFunction names do not.\n\n**Expand All Acronyms**\n\nAll acronyms must be fully expanded on first mention:\n\n```r\n# BAD\nDescription: Implements X-SAMPA processing.\n\n# GOOD\nDescription: Implements Extended Speech Assessment Methods Phonetic\n    Alphabet (X-SAMPA) processing.\n```\n\n**Publication Titles Only in Double Quotes**\n\nOnly use double quotes for publication titles, not for phrases or emphasis:\n\n```r\n# BAD\nDescription: Handles dates like \"the first Monday of December\".\n\n# GOOD\nDescription: Handles dates like the first Monday of December.\n```\n\n### URL and Link Validation\n\n**All URLs Must Use HTTPS**\n\nCRAN requires `https:\u002F\u002F` protocol for all URLs.\nHTTP links will be rejected.\n\n```r\n# BAD\nURL: http:\u002F\u002Fpaleobiodb.org\u002F\n\n# GOOD\nURL: https:\u002F\u002Fpaleobiodb.org\u002F\n```\n\n**No Redirecting URLs**\n\nCRAN rejects URLs that redirect to other locations.\nExample rejection:\n\n```\nFound the following (possibly) invalid URLs:\nURL: https:\u002F\u002Fh3geo.org\u002Fdocs\u002Fcore-library\u002Fcoordsystems#faceijk-coordinates\n     (moved to https:\u002F\u002Fh3geo.org\u002Fdocs\u002Fcore-library\u002Fcoordsystems\u002F)\n```\n\n**Use urlchecker Package**\n\n```r\n# Find redirecting URLs\nurlchecker::url_check()\n\n# Automatically update to final destinations\nurlchecker::url_update()\n```\n\n**Ignore URLs That Will Exist After Publication**\n\nSome URLs that don't currently resolve will exist once the package is published on CRAN.\nThese should NOT be changed:\n\n- CRAN badge URLs (e.g., `https:\u002F\u002Fcran.r-project.org\u002Fpackage=pkgname`)\n- CRAN status badges (e.g., `https:\u002F\u002Fwww.r-pkg.org\u002Fbadges\u002Fversion\u002Fpkgname`)\n- CRAN check results (e.g., `https:\u002F\u002Fcranchecks.info\u002Fbadges\u002Fpkgname`)\n- Package documentation URLs on r-universe or pkgdown sites that deploy after release\n\nWhen `urlchecker::url_check()` flags these URLs, leave them as-is.\nThey are aspirational URLs that will work once the package is on CRAN.\n\n**Check for Invalid File URIs**\n\nRelative links in README must exist after package build.\nCommon issue:\n\n```\nFound the following (possibly) invalid file URI:\n     URI: CODE_OF_CONDUCT.md\n       From: README.md\n```\n\nThis occurs when files are in `.Rbuildignore`.\nSolutions:\n1. Remove file from `.Rbuildignore`\n2. Use `usethis::use_code_of_conduct()` which generates sections without relative links\n\n### Administrative Requirements\n\n**Copyright Holder Role**\n\nAlways add `[cph]` role to Authors field, even if you're the only author:\n\n```r\n# Required\nAuthors@R: person(\"John\", \"Doe\", role = c(\"aut\", \"cre\", \"cph\"))\n```\n\n**Posit-Supported Packages**\n\nFor packages in Posit-related GitHub organizations (posit-dev, rstudio, r-lib, tidyverse, tidymodels) or maintained by someone with a @posit.co email address, include Posit Software, PBC as copyright holder and funder:\n\n```r\nAuthors@R: c(\n  person(\"Jane\", \"Doe\", role = c(\"aut\", \"cre\"),\n         email = \"jane.doe@posit.co\"),\n  person(\"Posit Software, PBC\", role = c(\"cph\", \"fnd\"),\n         comment = c(ROR = \"03wc8by49\"))\n)\n```\n\n**LICENSE Year**\n\nUpdate LICENSE year to current submission year:\n\n```r\n# If LICENSE shows 2024 but submitting in 2026\n# Update: 2024 → 2026\n```\n\n**Method References**\n\nCRAN may ask:\n\n> If there are references describing the methods in your package, please add these in the description field...\n\nIf there are no references, reply to the email explaining this.\nConsider adding a preemptive note in `cran-comments.md`:\n\n```markdown\n## Method References\n\nThere are no published references describing the methods in this package.\nThe package implements original functionality for [brief description].\n```\n\n## Key Files to Review\n\nWork through these files systematically:\n\n- **DESCRIPTION**: Title, Description, Authors@R, URLs, License year\n- **R\u002F*.R**: Function documentation (`@return`, `@examples`, `@examplesIf`, `@noRd`)\n- **README.Rmd** (if exists): Edit this file (NOT README.md), then run `devtools::build_readme()`\n- **README.md**: Review for install instructions, relative links, URLs.\n  Only edit directly if no README.Rmd exists\n- **cran-comments.md**: Preemptive notes for reviewers\n- **NEWS.md**: Version notes for this release\n- **.Rbuildignore**: Files referenced in README\n\n## Common Fix Patterns\n\n**DESCRIPTION Title:**\n```r\n# Before\nTitle: A Toolkit for the Construction of Modeling Packages for R\n\n# After\nTitle: Construct Modeling Packages\n```\n\n**DESCRIPTION Description:**\n```r\n# Before\nDescription: This package provides functions for rendering slides.\n\n# After\nDescription: Render slides to different formats including HTML and PDF.\n    Supports custom themes and progressive disclosure. Integrates with\n    'reveal.js' for interactive presentations.\n```\n\n**Function Documentation:**\n```r\n# Before - Missing @return\n#' Calculate total\n#' @param x Values\n#' @export\ncalc_total \u003C- function(x) sum(x)\n\n# After - Complete documentation\n#' Calculate total\n#' @param x Numeric values to sum\n#' @return A numeric value representing the sum\n#' @examples\n#' calc_total(1:10)\n#' @export\ncalc_total \u003C- function(x) sum(x)\n```\n\n## Useful Tools\n\nRunnable commands via `Rscript`:\n\n```bash\n# Check and update URLs\nRscript -e 'urlchecker::url_check()'\nRscript -e 'urlchecker::url_update()'\n\n# Scaffolding and formatting\nRscript -e 'devtools::build_readme()'\nRscript -e 'usethis::use_tidy_description()'\nRscript -e 'usethis::use_news_md()'\nRscript -e 'usethis::use_cran_comments()'\n```\n\n- `tools::toTitleCase()` - Format titles with proper capitalization\n- `urlchecker::url_check()` - Find problematic URLs\n- `urlchecker::url_update()` - Fix redirecting URLs\n- `usethis::use_news_md()` - Create NEWS.md\n- `usethis::use_cran_comments()` - Create cran-comments.md\n- `devtools::build_readme()` - Re-render README.md from README.Rmd\n- `usethis::use_code_of_conduct()` - Add CoC without relative links\n- `usethis::use_build_ignore()` - Ignore files in R package build\n- `usethis::use_package()` - Add a package dependency to DESCRIPTION\n- `usethis::use_tidy_description()` - Tidy up DESCRIPTION formatting\n\n## Final Verification Checklist\n\nUse this checklist to ensure nothing is missed before submission:\n\n### Files and Structure\n- [ ] `NEWS.md` exists and documents changes for this version\n- [ ] `cran-comments.md` exists with submission notes\n- [ ] If README.Rmd exists, it was edited (not README.md) and `devtools::build_readme()` was run\n- [ ] README includes valid install instructions (`install.packages(\"pkgname\")`)\n- [ ] README has no relative links (all links are full URLs or removed)\n\n### DESCRIPTION File\n- [ ] `Title:` uses title case\n- [ ] `Title:` has no redundant phrases (\"A Toolkit for\", \"Tools for\", \"for R\")\n- [ ] `Title:` quotes all software\u002Fpackage names in single quotes\n- [ ] `Title:` is under 65 characters\n- [ ] `Description:` does NOT start with \"This package\", package name, or \"Functions for\"\n- [ ] `Description:` is 3-4 sentences explaining purpose and utility\n- [ ] `Description:` quotes software\u002Fpackage\u002FAPI names (including 'R') but NOT function names\n- [ ] `Description:` expands all acronyms on first mention\n- [ ] `Description:` uses double quotes only for publication titles\n- [ ] `Authors@R:` includes copyright holder with `[cph]` role\n- [ ] For Posit packages: Includes `person(\"Posit Software, PBC\", role = c(\"cph\", \"fnd\"), comment = c(ROR = \"03wc8by49\"))`\n- [ ] LICENSE year matches current submission year\n\n### Function Documentation\n- [ ] All exported functions have `@return` documentation\n- [ ] All exported functions with meaningful returns have `@examples`\n- [ ] No example sections use commented-out code\n- [ ] Examples avoid `\\dontrun{}` unless truly necessary\n- [ ] Examples requiring suggested packages use `@examplesIf` or `if` guards\n- [ ] Un-exported functions with examples use `:::` notation or `@noRd`\n\n### URLs and Links\n- [ ] `urlchecker::url_check()` was run\n- [ ] All URLs use https protocol (no http links)\n- [ ] No redirecting URLs (except aspirational CRAN badge URLs)\n- [ ] Aspirational URLs (CRAN badges, etc.) are left as-is\n- [ ] No relative links in README that reference `.Rbuildignore` files\n\n### Optional but Recommended\n- [ ] If concerns about method references, added preemptive note to `cran-comments.md`\n- [ ] Reviewed bundled file licensing if including third-party files\n\n## Relationship to other skills\n\nThis is the ad-hoc \u002F stylistic checklist (Title case, `@return` tags, `\\dontrun{}` usage, URL hygiene) that `devtools::check()` doesn't catch on its own.\n[`r-pkg-cran-checklist`](..\u002Fr-pkg-cran-checklist\u002FSKILL.md) covers the release mechanics this skill does not: win-builder, revdep checks, and `devtools::release()`.\nRun both for a CRAN submission --- neither subsumes the other.\n","# CRAN Extra Checks\n\nHelp R package developers prepare packages for CRAN submission by systematically checking for common ad-hoc requirements that CRAN reviewers enforce but `devtools::check()` doesn't catch.\n\n## Workflow\n\n1. **Initial Assessment**: Ask user if this is first submission or resubmission\n2. **Run Standard Checklist**: Work through each item systematically (see below)\n3. **Identify Issues**: As you review files, note specific problems\n4. **Propose Fixes**: Suggest specific changes for each issue found\n5. **Implement Changes**: Make edits only when user approves\n6. **Verify**: Confirm all changes are complete\n\n## Standard CRAN Preparation Checklist\n\nWork through these items systematically:\n\n1. **Create NEWS.md**: Run `usethis::use_news_md()` if not already present\n2. **Create cran-comments.md**: Run `usethis::use_cran_comments()` if not already present\n3. **Review README**:\n   - Ensure it includes install instructions that will be valid when the package is accepted to CRAN (usually `install.packages(\"pkgname\")`).\n   - Check that it does not contain relative links.\n     This works on GitHub but will be flagged by CRAN.\n     Use full URLs to package documentation or remove the links.\n   - Does the README clearly explain the package purpose and functionality?\n   - **Important**: If README.Rmd exists, edit ONLY README.Rmd (README.md will be overwritten), then run `devtools::build_readme()` to re-render README.md\n4. **Proofread DESCRIPTION**: Carefully review `Title:` and `Description:` fields (see detailed guidance below)\n5. **Check function documentation**: Verify all exported functions have `@return` and `@examples` (see detailed guidance below)\n6. **Verify copyright holder**: Check that `Authors@R:` includes a copyright holder with role `[cph]`\n7. **Review bundled file licensing**: Check licensing of any included third-party files\n8. **Run URL checks**: Use `urlchecker::url_check()` and fix any issues\n\n## Detailed CRAN Checks\n\n### Documentation Requirements\n\n**Return Value Documentation (Strictly Enforced)**\n\nCRAN now strictly requires `@return` documentation for all exported functions.\nUse the roxygen2 tag `@return` to document what the function returns.\n\n- Required even for functions marked `@keywords internal`\n- Required even if function returns nothing - document as `@return None` or similar\n- Must be present for every exported function\n\nExample:\n```r\n# Missing @return - WILL BE REJECTED\n#' Calculate sum\n#' @export\nmy_sum \u003C- function(x, y) {\n  x + y\n}\n\n# Correct - includes @return\n#' Calculate sum\n#' @param x First number\n#' @param y Second number\n#' @return A numeric value\n#' @export\nmy_sum \u003C- function(x, y) {\n  x + y\n}\n\n# For functions with no return value\n#' Print message\n#' @param msg Message to print\n#' @return None, called for side effects\n#' @export\nprint_msg \u003C- function(msg) {\n  cat(msg, \"\\n\")\n}\n```\n\n**Examples for Exported Functions**\n\nIf your exported function has a meaningful return value, it will almost definitely require an `@examples` section.\nUse the roxygen2 tag `@examples`.\n\n- Required even for functions marked `@keywords internal`\n- Exceptions exist for functions used purely for side effects (e.g., creating directories)\n- Examples must be executable\n\n**Un-exported Functions with Examples**\n\nIf you write roxygen examples for un-exported functions, you must either:\n\n1. Call them with `:::` notation: `pkg:::my_fun()`\n2. Use `@noRd` tag to suppress `.Rd` file creation\n\n**Using `\\dontrun{}` Sparingly**\n\n`\\dontrun{}` should only be used if the example really cannot be executed (e.g., missing additional software, API keys, etc.).\n\n- If showing an error, wrap the call in `try()` instead\n- Consider custom predicates (e.g., `googlesheets4::sheets_has_token()`) with `if ()` blocks\n- Sometimes `interactive()` can be used as the condition\n- Lengthy examples (> 5 sec) can use `\\donttest{}`\n\n**Never Comment Out Code in Examples**\n\n```r\n# BAD - Will be rejected\n#' @examples\n#' # my_function(x)  # Don't do this!\n```\n\nCRAN's guidance: \"Examples\u002Fcode lines in examples should never be commented out.\nIdeally find toy examples that can be regularly executed and checked.\"\n\n**Guarding Examples with Suggested Packages**\n\nUse `@examplesIf` for entire example sections requiring suggested packages:\n\n```r\n#' @examplesIf rlang::is_installed(\"dplyr\")\n#' library(dplyr)\n#' my_data %>% my_function()\n```\n\nFor individual code blocks within examples:\n```r\n#' @examples\n#' if (rlang::is_installed(\"dplyr\")) {\n#'   library(dplyr)\n#'   my_data %>% my_function()\n#' }\n```\n\n### DESCRIPTION Title Field\n\nCRAN enforces strict Title requirements:\n\n**Use Title Case**\n\nCapitalize all words except articles like 'a', 'the'.\nUse `tools::toTitleCase()` to help format.\n\n**Avoid Redundancy**\n\nCommon phrases that get flagged:\n- \"A Toolkit for\" → Remove\n- \"Tools for\" → Remove\n- \"for R\" → Remove\n\nExamples:\n```r\n# BAD\nTitle: A Toolkit for the Construction of Modeling Packages for R\n\n# GOOD\nTitle: Construct Modeling Packages\n\n# BAD\nTitle: Command Argument Parsing for R\n\n# GOOD\nTitle: Command Argument Parsing\n```\n\n**Quote Software\u002FPackage Names**\n\nPut all software and R package names in single quotes:\n\n```r\n# GOOD\nTitle: Interface to 'Tiingo' Stock Price API\n```\n\n**Length Limit**\n\nKeep titles under 65 characters.\n\n### DESCRIPTION Description Field\n\n**Never Start With Forbidden Phrases**\n\nCRAN will reject descriptions starting with:\n- \"This package\"\n- Package name\n- \"Functions for\"\n\n```r\n# BAD\nDescription: This package provides functions for rendering slides.\nDescription: Functions for rendering slides to different formats.\n\n# GOOD\nDescription: Render slides to different formats including HTML and PDF.\n```\n\n**Expand to 3-4 Sentences**\n\nSingle-sentence descriptions are insufficient.\nProvide a broader description of:\n- What the package does\n- Why it may be useful\n- Types of problems it helps solve\n\n```r\n# BAD (too short)\nDescription: Render slides to different formats.\n\n# GOOD\nDescription: Render slides to different formats including HTML and PDF.\n    Supports custom themes and progressive disclosure patterns. Integrates\n    with 'reveal.js' for interactive presentations. Designed for technical\n    presentations and teaching materials.\n```\n\n**Quote Software Names, Not Functions**\n\n```r\n# BAD\nDescription: Uses 'case_when()' to process data.\n\n# GOOD\nDescription: Uses case_when() to process data with 'dplyr'.\n```\n\nSoftware, package, and API names get single quotes (including 'R').\nFunction names do not.\n\n**Expand All Acronyms**\n\nAll acronyms must be fully expanded on first mention:\n\n```r\n# BAD\nDescription: Implements X-SAMPA processing.\n\n# GOOD\nDescription: Implements Extended Speech Assessment Methods Phonetic\n    Alphabet (X-SAMPA) processing.\n```\n\n**Publication Titles Only in Double Quotes**\n\nOnly use double quotes for publication titles, not for phrases or emphasis:\n\n```r\n# BAD\nDescription: Handles dates like \"the first Monday of December\".\n\n# GOOD\nDescription: Handles dates like the first Monday of December.\n```\n\n### URL and Link Validation\n\n**All URLs Must Use HTTPS**\n\nCRAN requires `https:\u002F\u002F` protocol for all URLs.\nHTTP links will be rejected.\n\n```r\n# BAD\nURL: http:\u002F\u002Fpaleobiodb.org\u002F\n\n# GOOD\nURL: https:\u002F\u002Fpaleobiodb.org\u002F\n```\n\n**No Redirecting URLs**\n\nCRAN rejects URLs that redirect to other locations.\nExample rejection:\n\n```\nFound the following (possibly) invalid URLs:\nURL: https:\u002F\u002Fh3geo.org\u002Fdocs\u002Fcore-library\u002Fcoordsystems#faceijk-coordinates\n     (moved to https:\u002F\u002Fh3geo.org\u002Fdocs\u002Fcore-library\u002Fcoordsystems\u002F)\n```\n\n**Use urlchecker Package**\n\n```r\n# Find redirecting URLs\nurlchecker::url_check()\n\n# Automatically update to final destinations\nurlchecker::url_update()\n```\n\n**Ignore URLs That Will Exist After Publication**\n\nSome URLs that don't currently resolve will exist once the package is published on CRAN.\nThese should NOT be changed:\n\n- CRAN badge URLs (e.g., `https:\u002F\u002Fcran.r-project.org\u002Fpackage=pkgname`)\n- CRAN status badges (e.g., `https:\u002F\u002Fwww.r-pkg.org\u002Fbadges\u002Fversion\u002Fpkgname`)\n- CRAN check results (e.g., `https:\u002F\u002Fcranchecks.info\u002Fbadges\u002Fpkgname`)\n- Package documentation URLs on r-universe or pkgdown sites that deploy after release\n\nWhen `urlchecker::url_check()` flags these URLs, leave them as-is.\nThey are aspirational URLs that will work once the package is on CRAN.\n\n**Check for Invalid File URIs**\n\nRelative links in README must exist after package build.\nCommon issue:\n\n```\nFound the following (possibly) invalid file URI:\n     URI: CODE_OF_CONDUCT.md\n       From: README.md\n```\n\nThis occurs when files are in `.Rbuildignore`.\nSolutions:\n1. Remove file from `.Rbuildignore`\n2. Use `usethis::use_code_of_conduct()` which generates sections without relative links\n\n### Administrative Requirements\n\n**Copyright Holder Role**\n\nAlways add `[cph]` role to Authors field, even if you're the only author:\n\n```r\n# Required\nAuthors@R: person(\"John\", \"Doe\", role = c(\"aut\", \"cre\", \"cph\"))\n```\n\n**Posit-Supported Packages**\n\nFor packages in Posit-related GitHub organizations (posit-dev, rstudio, r-lib, tidyverse, tidymodels) or maintained by someone with a @posit.co email address, include Posit Software, PBC as copyright holder and funder:\n\n```r\nAuthors@R: c(\n  person(\"Jane\", \"Doe\", role = c(\"aut\", \"cre\"),\n         email = \"jane.doe@posit.co\"),\n  person(\"Posit Software, PBC\", role = c(\"cph\", \"fnd\"),\n         comment = c(ROR = \"03wc8by49\"))\n)\n```\n\n**LICENSE Year**\n\nUpdate LICENSE year to current submission year:\n\n```r\n# If LICENSE shows 2024 but submitting in 2026\n# Update: 2024 → 2026\n```\n\n**Method References**\n\nCRAN may ask:\n\n> If there are references describing the methods in your package, please add these in the description field...\n\nIf there are no references, reply to the email explaining this.\nConsider adding a preemptive note in `cran-comments.md`:\n\n```markdown\n## Method References\n\nThere are no published references describing the methods in this package.\nThe package implements original functionality for [brief description].\n```\n\n## Key Files to Review\n\nWork through these files systematically:\n\n- **DESCRIPTION**: Title, Description, Authors@R, URLs, License year\n- **R\u002F*.R**: Function documentation (`@return`, `@examples`, `@examplesIf`, `@noRd`)\n- **README.Rmd** (if exists): Edit this file (NOT README.md), then run `devtools::build_readme()`\n- **README.md**: Review for install instructions, relative links, URLs.\n  Only edit directly if no README.Rmd exists\n- **cran-comments.md**: Preemptive notes for reviewers\n- **NEWS.md**: Version notes for this release\n- **.Rbuildignore**: Files referenced in README\n\n## Common Fix Patterns\n\n**DESCRIPTION Title:**\n```r\n# Before\nTitle: A Toolkit for the Construction of Modeling Packages for R\n\n# After\nTitle: Construct Modeling Packages\n```\n\n**DESCRIPTION Description:**\n```r\n# Before\nDescription: This package provides functions for rendering slides.\n\n# After\nDescription: Render slides to different formats including HTML and PDF.\n    Supports custom themes and progressive disclosure. Integrates with\n    'reveal.js' for interactive presentations.\n```\n\n**Function Documentation:**\n```r\n# Before - Missing @return\n#' Calculate total\n#' @param x Values\n#' @export\ncalc_total \u003C- function(x) sum(x)\n\n# After - Complete documentation\n#' Calculate total\n#' @param x Numeric values to sum\n#' @return A numeric value representing the sum\n#' @examples\n#' calc_total(1:10)\n#' @export\ncalc_total \u003C- function(x) sum(x)\n```\n\n## Useful Tools\n\nRunnable commands via `Rscript`:\n\n```bash\n# Check and update URLs\nRscript -e 'urlchecker::url_check()'\nRscript -e 'urlchecker::url_update()'\n\n# Scaffolding and formatting\nRscript -e 'devtools::build_readme()'\nRscript -e 'usethis::use_tidy_description()'\nRscript -e 'usethis::use_news_md()'\nRscript -e 'usethis::use_cran_comments()'\n```\n\n- `tools::toTitleCase()` - Format titles with proper capitalization\n- `urlchecker::url_check()` - Find problematic URLs\n- `urlchecker::url_update()` - Fix redirecting URLs\n- `usethis::use_news_md()` - Create NEWS.md\n- `usethis::use_cran_comments()` - Create cran-comments.md\n- `devtools::build_readme()` - Re-render README.md from README.Rmd\n- `usethis::use_code_of_conduct()` - Add CoC without relative links\n- `usethis::use_build_ignore()` - Ignore files in R package build\n- `usethis::use_package()` - Add a package dependency to DESCRIPTION\n- `usethis::use_tidy_description()` - Tidy up DESCRIPTION formatting\n\n## Final Verification Checklist\n\nUse this checklist to ensure nothing is missed before submission:\n\n### Files and Structure\n- [ ] `NEWS.md` exists and documents changes for this version\n- [ ] `cran-comments.md` exists with submission notes\n- [ ] If README.Rmd exists, it was edited (not README.md) and `devtools::build_readme()` was run\n- [ ] README includes valid install instructions (`install.packages(\"pkgname\")`)\n- [ ] README has no relative links (all links are full URLs or removed)\n\n### DESCRIPTION File\n- [ ] `Title:` uses title case\n- [ ] `Title:` has no redundant phrases (\"A Toolkit for\", \"Tools for\", \"for R\")\n- [ ] `Title:` quotes all software\u002Fpackage names in single quotes\n- [ ] `Title:` is under 65 characters\n- [ ] `Description:` does NOT start with \"This package\", package name, or \"Functions for\"\n- [ ] `Description:` is 3-4 sentences explaining purpose and utility\n- [ ] `Description:` quotes software\u002Fpackage\u002FAPI names (including 'R') but NOT function names\n- [ ] `Description:` expands all acronyms on first mention\n- [ ] `Description:` uses double quotes only for publication titles\n- [ ] `Authors@R:` includes copyright holder with `[cph]` role\n- [ ] For Posit packages: Includes `person(\"Posit Software, PBC\", role = c(\"cph\", \"fnd\"), comment = c(ROR = \"03wc8by49\"))`\n- [ ] LICENSE year matches current submission year\n\n### Function Documentation\n- [ ] All exported functions have `@return` documentation\n- [ ] All exported functions with meaningful returns have `@examples`\n- [ ] No example sections use commented-out code\n- [ ] Examples avoid `\\dontrun{}` unless truly necessary\n- [ ] Examples requiring suggested packages use `@examplesIf` or `if` guards\n- [ ] Un-exported functions with examples use `:::` notation or `@noRd`\n\n### URLs and Links\n- [ ] `urlchecker::url_check()` was run\n- [ ] All URLs use https protocol (no http links)\n- [ ] No redirecting URLs (except aspirational CRAN badge URLs)\n- [ ] Aspirational URLs (CRAN badges, etc.) are left as-is\n- [ ] No relative links in README that reference `.Rbuildignore` files\n\n### Optional but Recommended\n- [ ] If concerns about method references, added preemptive note to `cran-comments.md`\n- [ ] Reviewed bundled file licensing if including third-party files\n\n## Relationship to other skills\n\nThis is the ad-hoc \u002F stylistic checklist (Title case, `@return` tags, `\\dontrun{}` usage, URL hygiene) that `devtools::check()` doesn't catch on its own.\n[`r-pkg-cran-checklist`](..\u002Fr-pkg-cran-checklist\u002FSKILL.md) covers the release mechanics this skill does not: win-builder, revdep checks, and `devtools::release()`.\nRun both for a CRAN submission --- neither subsumes the other.\n",{"name":5,"license":15,"metadata":24,"description":7,"allowed-tools":27,"user-invocable":32},{"author":25,"version":26},"Garrick Aden-Buie (@gadenbuie)","1.0",[28,29,30,31],"Read","Edit","Write","Bash",true,"main","0f720481f8ce3b3d9fef485f6e230d8b3035748e","skills\u002Fcran-extrachecks",1,"https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config","https:\u002F\u002Fmorrison-lab.github.io\u002Fai-config\u002F","https:\u002F\u002Fgithub.com\u002FMorrison-Lab","2026-11-15 04:39:15",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":32},[43,46,49],{"tool":44,"command":45},"npx","npx skills add Morrison-Lab\u002Fai-config --skill cran-extrachecks",{"tool":47,"command":48},"bunx","bunx skills add Morrison-Lab\u002Fai-config --skill cran-extrachecks",{"tool":50,"command":51},"pnpm","pnpm dlx skills add Morrison-Lab\u002Fai-config --skill cran-extrachecks","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fcran-extrachecks\u002FSKILL.md",[],[55,62,69,76,83,90],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M735BVYCGR5VEC65AFDVSNKW","wrap-up","End-of-session verification and UMS.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fwrap-up\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M735BTH469T1CQ8G2Q9GENCR","workaround-watcher","Watch upstream issue for fix.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fworkaround-watcher\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M735BRKZWFANSQ0GM380B4TD","wn","→ whats-next.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fwn\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M735BPE9V830B3B6NGXQ56J6","whats-next","Recommend concrete next step or action.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fwhats-next\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M735BMHQ60EAD5B7QAWXC5A0","wait-for-results","Wait for pipeline\u002FCI results.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fwait-for-results\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M735BKGZHPN1PEMJ7YBD5VJ8","wai","→ send-notes.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fwai\u002FSKILL.md",[],[]]