r-package-development

To structure a new R package, scaffold a root directory containing DESCRIPTION, NAMESPACE, and an R/ folder. Use roxygen2 for inline documentation and testthat to implement testing schemas, ensuring reproducible builds and maintainable code.

Managing dependencies in an R package DESCRIPTION file requires specifying package names and version requirements. This Skill enforces concrete requirements for DESCRIPTION fields to ensure robust dependency tracking and reproducible builds across different environments.

NAMESPACE export management with roxygen2 uses inline tags to define exported functions. This approach standardizes API design by automatically generating NAMESPACE directives, ensuring stable and well-documented interfaces for your R package.

The best way to document R package functions is using roxygen2 tags for examples and creating vignettes for broader usage guides. This ensures long-term project health by providing comprehensive, maintainable documentation for users.

Yes, you can apply this workflow to existing R packages to standardize API design and testing. It guides updates to project structure, roxygen2 documentation, testthat tests, and DESCRIPTION management for better maintainability.

Standardizing R package development solves the problem of inconsistent project structures and documentation. By detailing dependencies, API design, testing, and documentation, it enforces concrete requirements that ensure robust, reproducible builds across all projects.