skills.rest
Zepeng-Mu
Zepeng-MuCOMMUNITY
Explore all skills by this author →
Website𝕏@ZepengMuGitHub

r-code-reviewer

Review R package code for redundancy and roxygen2 documentation quality.

1|Updated Sep 1, 2025
Search Tags:#code quality#code review#documentation#refactoring#r#package development
One-click install
npx skills add https://github.com/Zepeng-Mu/ezGenomeTracks --skill r-code-reviewer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: r-code-reviewer
Source: https://github.com/Zepeng-Mu/ezGenomeTracks/tree/main/.github/skills/r-code-reviewer
Command: npx skills add https://github.com/Zepeng-Mu/ezGenomeTracks --skill r-code-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenges of maintaining high-quality, efficient, and well-documented R packages by systematically reviewing code for common issues.

Core Features & Use Cases

  • Code Quality Analysis: Identifies redundancy, suggests simplifications, and enforces consistency.
  • Documentation Enhancement: Ensures comprehensive and clear documentation using roxygen2 standards.
  • Use Case: A developer can use this Skill to get a detailed report on potential improvements for their R package before release, ensuring it meets professional standards for readability, reusability, and maintainability.

Quick Start

Review the R code in the current directory for redundancy and documentation quality.

Frequently Asked Questions about r-code-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review R package code for redundancy and documentation quality?▼

Reviewing R package code involves static analysis to identify redundancy, suggest simplifications, and enforce roxygen2 documentation standards, ensuring readability and maintainability before release.

What's the best way to improve R package documentation using roxygen2?▼

Improving R package documentation with roxygen2 requires systematically checking code to ensure comprehensive and clear standards are met, enhancing reusability and maintainability for professional release.

Do I need devtools and lintr to check R package code quality?▼

Yes, checking R package code quality requires tools like devtools, styler, and lintr for comprehensive package assessment, static analysis, and enforcing best practice standards.

How does static analysis simplify R package implementations?▼

Static analysis simplifies R package implementations by identifying redundancy and rectifying complex code structures, promoting consistency and reusability across the package development workflow.

Can I use this R code review workflow before package release?▼

Yes, you can use this R code review workflow before release to get a detailed report on potential improvements, ensuring the package meets professional standards for readability and maintainability.

When should I refactor R code for reusability?▼

You should refactor R code for reusability when static analysis identifies redundancy and inconsistency, ensuring the package adheres to best practices and roxygen2 documentation standards.

Related Skills

Explore More Software Engineering Skills→
ntluong95ntluong95

R Best Practices

Enforces idiomatic R coding standards for statistical analysis and package development.

Community
Basic
seabbsseabbs
7

r-development

Automate R package build, test, and documentation workflows with devtools, roxygen2, and testthat.

Community
Intermediate
sunzhksunzhk

R Code Style Skill

Enforce Google's R style guide on R codebases using styler and lintr.

Community
Intermediate
ab604ab604
189

r-package-development

Standardize R package development with roxygen2 documentation and testthat tests.

Community
Intermediate