What problem does it solve? R projects often suffer from inconsistent package versions across machines, unclear Imports versus Suggests placement, and broken renv lockfiles. This Skill defines a disciplined workflow for adding, updating, and troubleshooting R dependencies so environments stay reproducible. ## Core Features & Use Cases - renv lifecycle management: Covers init, install, snapshot, restore, update, remove, status, and clean operations with guidance on when to use each. - DESCRIPTION conventions: Enforces correct Imports/Suggests separation, minimum version bounds, alphabetization, and formatting rules. - Version pinning strategy: Distinguishes exact pins in renv.lock from minimum bounds in DESCRIPTION, including Bioconductor and GitHub sources. - Troubleshooting table: Maps common failures like restore errors, lockfile drift, and binary/source conflicts to concrete fixes. - Use Case: When adding the arrow package for parquet I/O, follow the five-step workflow to install it, register it in DESCRIPTION via usethis, snapshot the lockfile, verify with renv::status(), and commit both files with a conventional deps message. ## Quick Start Ask Claude to add the arrow package to your R project dependencies and update the renv lockfile.
