# Technical Contribution Guidelines

The best way to contribute to Omni X is to fork, fix, commit and create a pull request describing your work in detail. No matter what repository, please follow the following structure to create a description for a pull request:<br>

**Title (mandatory) --** The title of the fix/feature\
**Description (mandatory) --** Describe what work have you done in as much detail as possible.\
**Related Issue (optional) --** If the pull request fixes an issue please tag the id of this issue.\
**Context (mandatory) --** Write down the context behind this feature/fix, what was the purpose of implementing it?\
**How has this been tested? (mandatory) --** Describe what testing you have done to make sure that the fix/feature works as intended and does not break the existing code.\
**Screenshots (mandatory) --** Please include a screenshot of your work. A frontend fix/feature should directly include a screenshot of your work. A backend fix/feature can include a screenshot of the hardhat output after running a test.&#x20;


---

# Agent Instructions: 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:

```
GET https://docs.omni-x.io/omni-x/contribute/technical-contribution-guidelines.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.