Details how to query bitdrift documentation. Use when the user asks questions about how to use bitdrift, its features, or best practices, and when the user mentions /bd-docs.
To fetch a full dump of the bitdrift documentation, run the following cURL command in your terminal:
curl -L -H "Accept: text/markdown" https://docs.bitdrift.io
This is the only way that the documentation should be fetched.
The result will be a markdown file containing the entirety of the bitdrift documentation, which you can then search through or reference as needed. The original filenames are included for reference within the markdown content. These can be used to give a source url for the user to open and view the relevant documentation in their browser.
The full documentation dump is very large. To avoid pulling the entire output into context, pipe the curl command through grep to extract only the relevant sections:
curl -L -H "Accept: text/markdown" https://docs.bitdrift.io 2>/dev/null | grep -i -B 5 -A 50 'keyword1\|keyword2\|keyword3'
Use multiple alternate keywords to cast a wide net (e.g., deobfuscation\|symbol.*upload\|proguard\|dsym). Adjust -A (after) and -B (before) line counts as needed to capture full sections.
If the grep results are insufficient or you need broader context, fall back to fetching the full dump.
The markdown output contains file markers in the format ### File: <path> ### (e.g., ### File: sdk/issues.md ###). To construct a browsable URL for the user:
sdk/issues.md).md extensionhttps://docs.bitdrift.io/Example: ### File: sdk/issues.md ### → https://docs.bitdrift.io/sdk/issues/
Always include a source link when returning information from the documentation. Every answer should end with a reference to the relevant documentation page(s) so the user can verify the information at the source. Use the URL construction method described above to convert file markers into browsable links. If multiple pages were used, list all of them.