> For the complete documentation index, see [llms.txt](https://docs.bito.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bito.ai/ai-code-reviews-in-ide/ai-that-understands-your-code/available-keywords.md).

# Available Keywords

Keywords to invoke AI that understands your code

Here is the list of keywords in different languages to ask questions regarding your entire codebase. Use any of these keywords in your prompts inside Bito chatbox.

### English:&#x20;

* my code&#x20;
* my repo&#x20;
* my project&#x20;
* my workspace&#x20;

### Chinese:&#x20;

* 我的代码&#x20;
* 我的仓库&#x20;
* 我的代码库&#x20;
* 我的项目&#x20;
* 我的文件夹&#x20;

### Chinese Traditional:&#x20;

* 我的程式碼&#x20;
* 我的倉庫&#x20;
* 我的項目&#x20;
* 我的工作區&#x20;

### Spanish:&#x20;

* Mi código&#x20;
* Mi repo&#x20;
* Mi proyecto&#x20;
* Mi espacio de trabajo&#x20;

### Japanese:&#x20;

* 私のコード&#x20;
* 私のリポ&#x20;
* 私のプロジェクト&#x20;
* 私のワークスペース&#x20;

### Portuguese:&#x20;

* Meu código&#x20;
* Meu repo&#x20;
* Meu projeto&#x20;
* Meu espaço de trabalho

## Polish

* Mój obszar roboczy
* moje miejsce pracy
* mój obszar roboczy
* moj kod
* mój kod
* moim kodzie
* moje repo
* moje repozytorium
* moim repo
* moj projekt
* mój projekt
* moim projekcie


---

# 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.bito.ai/ai-code-reviews-in-ide/ai-that-understands-your-code/available-keywords.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.
