> For the complete documentation index, see [llms.txt](https://netstim.gitbook.io/leaddbs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://netstim.gitbook.io/leaddbs/ways-to-contribute-to-lead-dbs.md).

# How to contribute to Lead-DBS

We are grateful for any help in developing Lead-DBS. We have been coordinating the development on Slack, so get in touch with us to get an invite and join our monthly developer meetings. You are also welcome to clone or fork Lead-DBS from [Github](https://github.com/netstim/leaddbs) and submit pull requests.

You can also contribute to Lead-DBS with other things than code. For instance, maintaining this [user guide](https://netstim.gitbook.io/leaddbs/) or answering user questions on our [slack channel](https://www.lead-dbs.org/helpsupport/slack-user-channel/) is a great way to help and give back to the community. In addition, sharing data such as atlases, connectomes or clinical scores associated with VTAs are greatly appreciated.

##


---

# 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://netstim.gitbook.io/leaddbs/ways-to-contribute-to-lead-dbs.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.