> For the complete documentation index, see [llms.txt](https://docs.vale.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vale.sh/formats/rmarkdown.md).

# R Markdown

Learn how Vale handles R Markdown content.

{% hint style="info" %}
Requires Vale v3.18.0 or later. Earlier versions can assign the format instead: `Rmd = md` under `[formats]`.
{% endhint %}

[R Markdown](https://rmarkdown.rstudio.com/) is Markdown with knitr code chunks and inline R expressions. Vale reads it as [Markdown](/formats/markdown.md), and the knitr syntax is code to it:

* Chunks are fenced blocks: the chunk options in the `{r ...}` info string and everything inside the fence are ignored.
* Inline expressions such as `` `r nrow(df)` `` are code spans, and are ignored by default.

The supported extensions are `.Rmd` and `.rmd`. A configuration section still has to match one of them:

```ini
[*.{md,Rmd}]
BasedOnStyles = Vale
```

Pandoc syntax that is not Markdown, citations for one, can be excluded with [`TokenIgnores`](/keys/tokenignores.md):

```ini
[*.{md,Rmd}]
TokenIgnores = (\[@[^\n\]]+\])
```

Front matter, math, and comment-based configuration work as they do in [Markdown](/formats/markdown.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.vale.sh/formats/rmarkdown.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.