~ / rigs / ab604 / claude-code-r-skills

ab604/claude-code-r-skills

Claude Code configurations for R development.

↗ GitHub ★ 206 MIT updated 22d ago project Claude Code Claude plugin
share on X
ARCHETYPE
Pragmatist
A balanced, no-drama setup: some rules, some tools, nothing extreme.
CONTEXT TAX · EVERY TURN
~1.2k tokens
Featherweight · median rig: 2.3k · breakdown
GUARDRAILS
1/5
No YOLO mode · details

Copy this rig

# review before running: this installs third-party code
$ npx degit ab604/claude-code-r-skills/.claude ./rig-claude-code-r-skills  # inspect, then merge into .claude/

MCP servers are added to Claude Code at local scope; env vars are shown as YOUR_… placeholders — we never store values. Files are fetched with degit into a separate folder so you can review before merging.

$ npx degit ab604/claude-code-r-skills/.claude/skills/r-bayes .claude/skills/r-bayes
$ npx degit ab604/claude-code-r-skills/.claude/skills/r-oop .claude/skills/r-oop
$ npx degit ab604/claude-code-r-skills/.claude/skills/r-package-development .claude/skills/r-package-development
$ npx degit ab604/claude-code-r-skills/.claude/skills/r-performance .claude/skills/r-performance
$ npx degit ab604/claude-code-r-skills/.claude/skills/r-style-guide .claude/skills/r-style-guide
$ npx degit ab604/claude-code-r-skills/.claude/skills/rlang-patterns .claude/skills/rlang-patterns
$ npx degit ab604/claude-code-r-skills/.claude/skills/tdd-workflow .claude/skills/tdd-workflow
$ npx degit ab604/claude-code-r-skills/.claude/skills/tidyverse-patterns .claude/skills/tidyverse-patterns
$ curl -fsSL --create-dirs -o .claude/agents/code-reviewer.md https://raw.githubusercontent.com/ab604/claude-code-r-skills/main/agents/code-reviewer.md
$ curl -fsSL --create-dirs -o .claude/agents/planner.md https://raw.githubusercontent.com/ab604/claude-code-r-skills/main/agents/planner.md
$ curl -fsSL --create-dirs -o .claude/agents/tdd-guide.md https://raw.githubusercontent.com/ab604/claude-code-r-skills/main/agents/tdd-guide.md

This rig commits no guardrails. Here is the community baseline instead — the deny/ask rules most often found across all 6,974 rigs:

{
  "permissions": {
    "deny": [
      "Read(./.env)",
      "Read(**/.env)",
      "Read(~/.ssh/**)",
      "Bash(rm -rf *)",
      "Read(**/*.pem)",
      "Bash(rm -rf /)",
      "Bash(git push --force:*)",
      "Bash(sudo *)",
      "Read(~/.aws/**)",
      "Bash(rm -rf /*)",
      "Read(./.env.*)",
      "Read(.env)",
      "Bash(git push --force*)",
      "Bash(rm -rf:*)",
      "Read(**/.env.*)",
      "Read(**/*.key)",
      "Bash(sudo:*)",
      "Bash(git reset --hard*)",
      "Bash(git reset --hard:*)",
      "Read(.env.*)"
    ],
    "ask": [
      "Bash(git push:*)",
      "Bash(git push *)",
      "Bash(git commit:*)",
      "Bash(rm *)",
      "Bash(rm:*)",
      "Bash(npm publish:*)",
      "Bash(wget *)",
      "Bash(git rebase *)",
      "Bash(gh pr merge *)",
      "Bash(git commit *)"
    ]
  }
}

Skills (8)

Subagents (3)

code-reviewerSenior R code review specialist. Use after writing code to review for security, quality, and best practices before committing.
planner
model: opus
Expert planning specialist for R projects. Use for feature implementation, architectural changes, or complex refactoring. Automatically activated for planning tasks.
tdd-guideTest-driven development specialist for R. Enforces test-first development with testthat. Use when writing new features, fixing bugs, or refactoring code.

Slash commands (4)

/code-review/plan/tdd/verify

Similar rigs

copied ✓