> For the complete documentation index, see [llms.txt](https://docs.aeternity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aeternity.com/developer-documentation/aeternity/.github/contributing.md).

# Contributing to the Aeternity node

### Pull Requests

* [Squash your commits](https://stackoverflow.com/questions/5189560/squash-my-last-x-commits-together-using-git) to ensure each resulting commit is stable and can be tested.
* Include issue numbers in the PR title, e.g. "GH-128. Resolves issue #123".
* Follow the [Erlang mode for Emacs](http://erlang.org/doc/apps/tools/erlang_mode_chapter.html) indentation, e.g. provided by [EDTS](https://github.com/tjarvstrand/edts).
* Add unit tests for self-contained modules.
* Add integration tests as needed.
* Document new code.
* End all files with a newline

### Git Commit Messages

* Use the present tense ("Add feature" not "Added feature")
* Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
* Limit the first line to 72 characters or less
* Reference issues and pull requests liberally after the first line

Learn more about [writing a good commit message](https://chris.beams.io/posts/git-commit/).


---

# 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.aeternity.com/developer-documentation/aeternity/.github/contributing.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.