claude

rforge

RForge toolkit for Claude Code: 44 commands for R package development, ecosystem management, CRAN submission, and intelligent orchestration

2 on GitHubby Data-Wisev2.22.2MITupdated 12 days agodevelopment
/

Plugin rforge from marketplace data-wise-rforge in Data-Wise/rforge. Commands read from the repo's manifest — 12 days ago.

What it installs

Skills (4)

  • review-fix-loop

    Run an adversarial review after a phase of work, triage each finding against the source, plan the fixes, implement them, and verify the result. Use whenever the user asks for an adversarial or Codex review of a phase or commit range, says to "review and fix", "run the review loop", or wants findings

  • rforge-check

    Run Rforge R package checks and explain errors, warnings, and NOTEs. Use for R CMD check or CRAN-style package validation.

  • rforge-docs-check

    Audit R package README and vignette calls against exported API signatures using Rforge. Use to find stale argument names, arity mismatches, or undocumented new exports since a comparison ref.

  • rforge-lint

    Run Rforge package lint and diagnose differences from CI, including missing names in test helpers and stale installed packages.

Slash commands (47)

  • /rforge:analyze

    Analyze R package ecosystem with mode-specific behavior depth

  • /rforge:capture

    Quick capture ideas and tasks for later (with automatic doc cascade detection)

  • /rforge:cascade

    Plan coordinated updates across dependent packages

  • /rforge:complete

    Mark tasks complete with automatic documentation cascade

  • /rforge:deps

    Build and visualize dependency graph across R package ecosystem

  • /rforge:detect

    Auto-detect R package project structure (single package, ecosystem, or hybrid)

  • /rforge:doc-check

    ⚠️ RENAMED to /rforge:docs:check in v2.0.0 — see migration tutorial

  • /rforge:docs:check

    Audit documentation content against the package API — calls and signatures in README/vignettes that no longer match the exports

  • /rforge:ecosystem-health

    ⚠️ RENAMED to /rforge:health in v2.0.0 — see migration tutorial

  • /rforge:finish

    Sync a single R package's .STATUS from its current state — diff-gated, never auto-applies

  • /rforge:health

    Check health across R package ecosystem

  • /rforge:impact

    Analyze change impact across ecosystem packages

  • /rforge:init

    Initialize rforge context for an R package directory (idempotent)

  • /rforge:next

    Get ecosystem-aware next task recommendation

  • /rforge:quick

    Ultra-fast ecosystem snapshot using only quick lib modules (< 10 seconds)

  • /rforge:r:build

    Build an R package tarball (pkgbuild) and report the artifact

  • /rforge:r:check

    Run R CMD check with smart parsing — NOTEs classified as spurious or real

  • /rforge:r:coverage

    Test coverage (covr) — total, per-file, and untested lines

  • /rforge:r:cran-prep

    Per-package CRAN gate — document→lint→spell→urlcheck→test→coverage→check (+strict noSuggests/suggests-only passes)→Tier 4 advisory→revdep, writes cran-comments.md

  • /rforge:r:cycle

    Full dev cycle — document → test → check (stops at first error)

  • /rforge:r:deps-sync

    Reconcile DESCRIPTION against actual code usage (missing/unused/misclassified deps)

  • /rforge:r:document

    Regenerate Rd docs and NAMESPACE (roxygen2)

  • /rforge:r:goodpractice

    Advisory best-practice bundle — goodpractice checks (opt-in, not part of r:cycle)

  • /rforge:r:install

    Install the package locally (R CMD INSTALL) and report version

  • /rforge:r:lint

    Static analysis of the package (lintr) — grouped report

  • /rforge:r:load

    Load the package into a namespace (pkgload::load_all) for dev

  • /rforge:r:revdep

    Reverse-dependency check against CRAN downstream packages (revdepcheck)

  • /rforge:r:rhub

    Multi-platform checks via R-hub v2 (rhub::rhub_check) — async, GitHub Actions

  • /rforge:r:s7-review

    Static S7 OOP convention checker (advisory — naming/validators/methods/legacy/docs)

  • /rforge:r:site

    Build the pkgdown website (vignettes→articles); optional preview

  • /rforge:r:spell

    Spell-check the package (spelling) and triage typos

  • /rforge:r:style

    Auto-format the package (styler) and show the diff

  • /rforge:r:submit

    GitHub pre-release of the submitted tarball + CRAN submit handoff; promote on acceptance

  • /rforge:r:test

    Run package tests (testthat) and report pass/fail/skip counts

  • /rforge:r:tidy

    Tidyverse-conventions audit — lint preset + DESCRIPTION normalization preview + roxygen completeness + NEWS.md header (advisory, never blocks)

  • /rforge:r:urlcheck

    Check package URLs for breakage/redirects (urlchecker)

  • /rforge:r:use-citation

    Scaffold inst/CITATION from DESCRIPTION (Title/Authors@R/Version, deterministic year)

  • /rforge:r:use-data

    Scaffold roxygen docs for a package dataset (R/data.R) and patch DESCRIPTION (LazyData/Depends)

  • /rforge:r:use-package

    Add a declared dependency (Imports vs Suggests, AI-picked) and an @importFrom tag

  • /rforge:r:use-test

    Scaffold a testthat file and draft test_that() blocks for a function (assertions left as TODO)

  • /rforge:r:use-vignette

    Scaffold a vignette skeleton (usethis infra) and draft an outline from the package purpose

  • /rforge:r:winbuilder

    Submit to win-builder (devel/release/oldrelease or R-hub) — async

  • /rforge:release

    Plan CRAN submission sequence based on dependencies

  • /rforge:restore

    Recap a single R package's state (DESCRIPTION, NEWS.md, git, .STATUS) — read-only except an explicitly-confirmed .STATUS scaffold offer

  • /rforge:rpkg-check

    ⚠️ RENAMED to /rforge:r:check in v2.0.0 — see migration tutorial

  • /rforge:status

    Ecosystem-wide status dashboard (health, packages, .STATUS aggregation)

  • /rforge:thorough

    Comprehensive ecosystem rollup — status, deps, cross-package health, and CRAN submission order

Subagents (1)

  • orchestrator

    R-package ecosystem orchestrator. Recognizes the intent behind a request (code change / impact, new function, bug fix, deps audit, quality, CRAN readiness, ecosystem health) and runs the matching rforge lib.* analyses via Bash, then synthesizes the JSON envelopes into one ADHD-friendly summary. Only

View source on GitHub data-wise.github.io

Similar plugins

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

context7

claudecodex

Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.

1 MCP server

upstash/context7 64,709

Build powerful, stateful CLI interfaces for any GUI application using the cli-anything harness methodology.

5 commands

HKUDS/CLI-Anything 58,665

Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer

8 skills · 1 MCP server

ChromeDevTools/chrome-devtools-mcp 55,181

Automates browser interactions for web testing, form filling, screenshots, and data extraction

12 skills

vercel-labs/agent-browser 50,373

Use Alibaba Open Code Review from local Codex.

2 skills

alibaba/open-code-review 50,068

Maintain rforge?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted