# Guidelines

### Contributing Guidelines

1. Fork the repository and create a new branch for your contribution.
2. Follow the coding guidelines for your code.
3. Test your code before committing and pushing it.
4. Use [semantic](https://gist.github.com/joshbuchea/6f47e86d2510bce28f8e7f42ae84c716) commit messages for your commits.

### Coding Guidelines

* Use the same code style and formatting as the rest of the project.
  * Optional: Use an IDE that supports `.editorconfig` files.
* Use meaningful names for variables, classes, and methods.
* Write clear comments to explain complex parts of your code.
* Ensure your code is easy to read and maintain.


---

# 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.jonesdev.xyz/contributing/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.