> For the complete documentation index, see [llms.txt](https://docs.speedb.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.speedb.io/getting-started/how-to-contribute/help-with-new-and-ongoing-feature-development.md).

# Help with new and ongoing feature development

If you find a feature request that you'd like to work on, and there's a pull request open for it, you can help by testing it and providing feedback. When giving feedback, please keep comments positive and constructive.

### How to check out a pull request

Every pull request has its own number, which  is visible both in the URL\
of a pull request page as well as in the title of the pull request page itself\
(the format is **#123**, where 123 is the PR number). 

To check out a pull request locally, [follow this guide](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally). 

If you're using GitHub CLI, be sure to choose the **GitHub CLI** option rather than **Web Browser** on the guide page. Once you have the pull request changes checked out locally, you can move on to\
[testing the changes](/getting-started/how-to-contribute/contribute-code.md#unit-tests).


---

# 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://docs.speedb.io/getting-started/how-to-contribute/help-with-new-and-ongoing-feature-development.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.