r-package-check-notesDrive R CMD check to zero errors, warnings and notes in a package that sets enforce-note-blocklist — the eight blocked NOTE patterns, what causes each, and how to fix it. Use when R CMD check fails, when a CI check job reports a NOTE, or when cleaning up a package before release or CRAN submission.
r-package-ci-gatesMap of the insightsengineering/r.pkg.template CI jobs (R CMD check, non-CRAN check, coverage, linter, roxygen, gitleaks, spelling, links, version, version bump, licenses, grammar) — what each enforces, when it runs, and how to reproduce it locally before pushing. Use when working in an R package tha
r-package-collaborationPut an R package under version control and ship it — git/GitHub setup and SSH keys, branch and pull-request workflow, semantic versioning, git tags and GitHub releases, GitHub Actions CI via r-lib/actions, and a pkgdown documentation site on GitHub Pages. Use when the user asks to version, tag, rele
r-package-initScaffold and structure a new R package the "good software engineering practice" way — design docs, usethis setup, DESCRIPTION fields, R/ and roxygen2 documentation, NAMESPACE, tests/data/vignettes folders, and the document-check-build-install loop. Use when the user wants to create a new R package,
r-package-qualityRaise the quality of an R package — apply clean code rules (CCR#1-10), write testthat unit/integration/snapshot tests, raise coverage with covr, format with styler and lint with lintr, and gate on devtools::check(). Use when the user asks to refactor, test, lint, add assertions, improve coverage, or