Ali Talha Yurtseven
Ali Talha Yurtseven's work was selected for the XERJ Corpus Hub, the open reference memory AI coding agents search before they write code. When an agent meets the same problem, it gets this implementation back as a worked example, with the author and the repository attached.
Totals across every corpus @alitalhq appears in; a commit selected for two corpora counts once. Files and lines count the selected commits; each corpus indexes the whole repository at its pinned commit.
What an agent can do with the bothy corpus
bothy-sync/bothy: bothy-sync/bothy (Rust)
- Reuse a worked example: the commit “add local SQLite store” (10 files · Rust).
- Answer from bothy's real Rust source instead of memory (API design and specification).
- Where does bothy handle “add local SQLite store”?
- What does crates/bothy do in bothy?
Search the GitHub repository bothy-sync/bothy with XERJ (https://hub.xerj.org/corpus/bothy-sync--bothy). Run these in a shell, in order, and check each result before the next: 1. xerj --help (success: it prints usage). If xerj is missing: curl -fsSL https://xerj.org/get | sh 2. git clone https://github.com/bothy-sync/bothy bothy && git -C bothy checkout 6c9bf9a210eb7a1db6ae98978222e4b07bf09df8 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./bothy --url http://127.0.0.1:9200 --prefix bothy --progress plain 5. xerj autoindex map --url http://127.0.0.1:9200 Then answer my question from the indexed files and cite the ax_path of every hit. Query syntax: https://xerj.org/llms.txt Licence: Apache-2.0. Keep the copyright notice and credit the authors.
corpus bothy-sync--bothy · API design and specification
Related corpora: libopenapi, openapi-overlay-spec, github-api-description, grpc-proposals
Search an OpenAPI spec from an agent · Case study: reference coding for agents
Selected work
bothy-sync/bothy
The corpus is the whole repository at the pinned commit, not only the files of the selected commit.
Not installable yet: this corpus is not in the hub registry until its licence review passes, so xerj corpus add and xerj ask cannot fetch it. It becomes installable when this card says live in the hub.
Sign in with GitHub or Hugging Face to see more: every selected commit in full (commit date, every folder, licence review state, pin) and the pack builds of each corpus.
[](https://hub.xerj.org/contributors/alitalhq)
Included with the author's permission (email, 2026-10-22), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.