> For the complete documentation index, see [llms.txt](https://omori-modding.gitbook.io/wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://omori-modding.gitbook.io/wiki/getting-started/source-control-with-github/using-repositories.md).

# Using Repositories

Let’s practice pushing to our repository. I’m going to do something simple: add a new image file to the img/characters folder. Let’s see what that looks like in GitHub Desktop.

<figure><img src="/files/f3Mob2tsj9I3EjOkSsSV" alt=""><figcaption></figcaption></figure>

It shows me a preview of what I’ve added! This is super helpful when I’m trying to see what I’ve added without having to navigate the folder.

GitHub does the same thing for most file types (pretty much all file types you’ll work with in basic OMORI modding). In the sidebar, it shows you what files you’ve added and their file paths, and once selected, shows you a preview of what you’ve added into the repository.

<br>


---

# 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://omori-modding.gitbook.io/wiki/getting-started/source-control-with-github/using-repositories.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.