> For the complete documentation index, see [llms.txt](https://docs.aviator.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aviator.co/aviator-cli/how-to-guides/use-editor-plugins.md).

# How to Use Editor Plugins in CLI

## Pull-Request Title and Description Editing

When editing the Pull-Request title and description, the Aviator CLI creates a temporary file with a file extension `.av.md`. Most of the text editors recognize this as a Markdown file, and the file is mostly highlighted accordingly. However, this file treats `%%` as a line comment, which is not a part of Markdown, and these parts are not highlighted properly.

By making an editor recognize `.av.md` as a special Markdown file, you can get a better text highlighting.

#### Vim

Install [<mark style="color:blue;">https://github.com/aviator-co/av-vim-plugin</mark>](https://github.com/aviator-co/av-vim-plugin) as a Vim plugin. This plugin detects `.av.md` as `av-markdown` syntax, and it does a proper syntax highlighting as well as setting a line comment prefix. Use a Vim plugin manager to install this. For example, if you use [<mark style="color:blue;">vim-plug</mark>](https://github.com/junegunn/vim-plug):

```
Plug 'aviator-co/av-vim-plugin'
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.aviator.co/aviator-cli/how-to-guides/use-editor-plugins.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.