mlr-org

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.

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.

Diagnose and fix CI failures in the mlr3book's render workflows (build-book, book-weekly, book-dev-weekly). Use when the user mentions mlr3book CI failures, the book not rendering, a weekly build failing, or asks to "fix the book", "check the book CI", or "maintain the mlr3book".

Review new chapters and sections in the mlr3book for compliance with the book's style guide and chapter structure requirements. Use when the user wants to review a chapter, section, or .qmd file from the mlr3book. Checks R code style, English writing conventions, Quarto formatting rules, and required chapter structure (front matter, introduction, conclusion) defined in the mlr3book style guide (https://github.com/mlr-org/mlr3book/issues/434) and structure guide (https://github.com/mlr-org/mlr3book/issues/435).

Maintain the mlr3 gallery by fixing broken posts and updating the Docker image. Invoked when gallery posts fail to render or need to be updated.

Review new gallery posts on the mlr-org.com website for compliance with the style guide. Use when the user wants to review a gallery post. Checks R code style, English writing conventions, Quarto formatting rules, and required structure.