r-package-check · git:20261106.a8c8716 · 2026-11-06 · sha256 c955bddc230c3c27
r-package-check git:20261106.a8c8716A
Immutable. This exact content never changes and is served at /api/v1/blob/c955bddc230c3c27.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_zrjyuot6eco6uawo/c955bddc230c3c278fadfc2ab55674ad9dfd0bfcb3593c458456a8d7bab27517.json
Then /plugin install r-package-check@markdownregistry-zrjyuot6eco6uawo in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: r-package-check description: Run the full R package release gate — regenerate docs, run the test suite, run R CMD check --as-cran, and triage every ERROR / WARNING / NOTE against CRAN policy before a release or submission. Use when the user says "check my R package", "R CMD check", "is this package CRAN-ready", "run devtools::check", "prepare for CRAN submission", or points at a directory containing a DESCRIPTION file. Produces a check report + CRAN-submission checklist in `quality_reports/`. --- <!-- Generated by scripts/sync-agent-skills.py from .claude/skills/r-package-check/SKILL.md. Do not edit: change the source and re-run the script. --> # r-package-check This skill's instructions live in [`.claude/skills/r-package-check/SKILL.md`](../../../.claude/skills/r-package-check/SKILL.md). Read that file now and follow it, with the files it points to. Read [`AGENTS.md`](../../../AGENTS.md) first if you have not already. It was written for Claude Code. Running it from Codex, Antigravity or another agent: - **Arguments.** Where it says `$ARGUMENTS`, use what the user asked for. - **Claude Code agents.** Where a step hands work to an agent in `.claude/agents/` (through the `Agent` or `Task` tool), do that step where it appears in the procedure: never later, and never skip it. A step that gates what follows still gates it (`/commit` runs its verifier before it commits). Read the agent's file for what the step checks. - **Fresh context.** If the step needs a context that has not seen your work, for example a claim verifier that must never see the draft, run it in a separate session or worker that has not seen the draft, if your tool can start one, and give it only what the step says to pass. If it cannot, do the step yourself, mark every result it produced *not independently verified*, and tell the user to repeat that check in Claude Code (`/verify-claims` for citations) before relying on it. - **Claude Code settings.** `allowed-tools`, `model`, `effort`, `argument-hint` and `disable-model-invocation` in the source's frontmatter configure Claude Code. Ignore them. - **Guards.** Claude Code's guard hooks do not run for you. Follow the rules in `AGENTS.md` yourself; the git pre-commit gate and CI still apply to your commits.