R Code Style Skill

To enforce Google R style guide rules, this skill checks your R codebase for naming, assignment, and namespace conventions to improve consistency and readability across package development and data analysis scripts.

R function naming conventions require BigCamelCase for public functions and a leading dot prefix for private helpers to clearly distinguish scope and improve code readability.

Yes, you need lintr and styler to check R code quality, as this skill relies on them to perform automated linting and apply style formatting for consistent codebase standards.

To prevent silent failures in R scripts, enforce explicit returns, explicit boundary validation, and explicit documentation, while actively discouraging risky patterns like attach() and silent global state modifications.

Explicit namespace usage in R reduces dependency conflicts and prevents silent masking errors by clearly specifying package origins, keeping imports minimal and code execution reliable.

Yes, you can use this R linting skill for package development, as it applies project-level coding standards to guide dependencies, naming, and documentation checks across your entire codebase.