> 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

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: 

* my code 
* my repo 
* my project 
* my workspace 

### Chinese: 

* 我的代码 
* 我的仓库 
* 我的代码库 
* 我的项目 
* 我的文件夹 

### Chinese Traditional: 

* 我的程式碼 
* 我的倉庫 
* 我的項目 
* 我的工作區 

### Spanish: 

* Mi código 
* Mi repo 
* Mi proyecto 
* Mi espacio de trabajo 

### Japanese: 

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

### Portuguese: 

* Meu código 
* Meu repo 
* Meu projeto 
* 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 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.bito.ai/ai-code-reviews-in-ide/ai-that-understands-your-code/available-keywords.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.