菜单
Spellcheck an R package with cspell, fix genuine typos in source files, and add legitimate domain words to .cspell/project-words.txt. Use when the user asks to spellcheck the package, run cspell, fix typos, or clean up the project dictionary.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | r-package-spellchecker |
| description | Spellcheck an R package with cspell, fix genuine typos in source files, and add legitimate domain words to .cspell/project-words.txt. Use when the user asks to spellcheck the package, run cspell, fix typos, or clean up the project dictionary. |
Spellcheck the package with cspell, fix genuine typos, and add legitimate words to the shared project dictionary.
The cspell configuration lives in cspell.json at the package root.
It checks markdown, plaintext, and .qmd files, plus comments (including roxygen) in R files.
The shared dictionary is .cspell/project-words.txt.
Run cspell from the package root (the config is auto-detected):
# Issues with file/line locations for context
npx --yes cspell --no-progress --relative .
# Deduplicated list of unknown words
npx --yes cspell --no-progress --words-only --unique . | sort -fu
Triage each unknown word using its source context (read the surrounding line in the reporting file when unsure):
.cspell/project-words.txt.
Examples: package, class, and function names (bbotk, Classif, clbk),
math and optimization jargon (codomain, BOBYQA),
author surnames from the bibliography (Bischl, Birattari),
and established abbreviations (evals).Apply the fixes, respecting these rules:
README.Rmd and regenerate with Rscript -e "devtools::build_readme()", never edit README.md directly. man/ and *.Rd are already ignored by the config.Rscript -e "devtools::document()"..cspell/project-words.txt one word per line, sorted alphabetically case-insensitively, below the existing header comments.Verify: re-run cspell until it reports no unknown words and exits 0.
Report: summarize the typos fixed (file: old → new) and the words added to the dictionary.
Prepare a CRAN release of packages in the mlr3 ecosystem.
Creates or bootstraps R packages by applying the shared template files from `package/`, including editor, lint, build, and AI guidance config.` rules copied into a target package.
Comprehensive guidance for Quarto document authoring and R Markdown migration. Use this skill when: (1) Writing new Quarto documents (.qmd) with best practices, (2) Converting R Markdown (.Rmd) documents to Quarto, (3) Migrating bookdown, blogdown, xaringan, or distill projects to Quarto, (4) Understanding Quarto's code cell syntax with hashpipe (#|) options, (5) Setting up cross-references for figures, tables, sections, and equations, (6) Using Quarto-specific markdown features like callouts, divs, and spans, (7) Configuring YAML front matter for documents and projects, (8) Finding and using Quarto extensions.
Name all unnamed or incorrectly named R code chunks in a .qmd file using the pattern `[file-name]-[number]` (e.g. `intro-001`, `intro-002`). Use when the user wants to add or standardize chunk labels in a Quarto file.
Prepare R packages for CRAN submission by checking for common ad-hoc requirements not caught by devtools::check(). Use when: (1) Preparing a package for first CRAN release, (2) Preparing a package update for CRAN resubmission, (3) Reviewing a package to ensure CRAN compliance, (4) Responding to CRAN reviewer feedback. Covers documentation requirements, DESCRIPTION field standards, URL validation, examples, and administrative requirements.
Creates a pull request from current changes, monitors GitHub CI, and debugs any failures until CI passes. Use this when the user says "create pr", "make a pr", "open pull request", "submit pr", "pr for these changes", or wants to get their current work into a reviewable PR. Assumes the project uses git, is hosted on GitHub, and has GitHub Actions CI with automated checks (lint, build, tests, etc.). Does NOT merge - stops when CI passes and provides the PR link.