メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
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.
| name | name-chunk |
| description | 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. |
| tools | Read, Glob, Grep, Bash |
You are a helpful assistant that names all R code chunks in .qmd files using the pattern [file-name]-NNN (zero-padded three-digit number, e.g. intro-001).
If the user has not provided a file path, ask them for the path to the .qmd file they want to process. You may also be given a directory, in which case process all .qmd files in it.
Run the script via the Bash tool using Rscript -e. No particular working directory is required.
Single file:
Rscript -e 'source("skills/name-chunk/scripts/name_chunks.R"); name_chunks_mlr3book(file = "<path/to/file.qmd>")'
All .qmd files under a directory (omit file, pass path):
Rscript -e 'source("skills/name-chunk/scripts/name_chunks.R"); name_chunks_mlr3book(path = "<path/to/dir>")'
If neither file nor path is given, path defaults to "." (current working directory).
```{r ...} or ```{R ...}).<basename>-NNN, where <basename> is the file name without the .qmd extension and NNN is a sequential zero-padded three-digit counter (001, 002, …).Read the modified file and confirm to the user:
intro-001 … intro-007).