yash.
yash.'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 @Yashbhu 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 FORGEqueue corpus
Yashbhu/FORGEqueue: A distributed task queue built from scratch in Go with worker leases, heartbeats, retries, delayed jobs, dead-letter queues, and…
- Reuse a worked example: the commit “v1.0-hardening: durable redis+postgres journal, gRPC auth, hardened i…” (63 files · Go, TypeScript).
- Answer from FORGEqueue's real Go source instead of memory (API design and specification).
- What does internal/auth do in FORGEqueue?
Search the GitHub repository Yashbhu/FORGEqueue with XERJ (https://hub.xerj.org/corpus/yashbhu--forgequeue). 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/Yashbhu/FORGEqueue FORGEqueue && git -C FORGEqueue checkout b91ecb5ce84503e814a627c26e268e892589a341 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./FORGEqueue --url http://127.0.0.1:9200 --prefix forgequeue --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 yashbhu--forgequeue · API design and specification
Related corpora: graphql-composite-schemas-spec, adyen-openapi, digitalocean-openapi, grpc-gateway
Search an OpenAPI spec from an agent · Case study: reference coding for agents
Selected work
Yashbhu/FORGEqueue
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/Yashbhu)
Included with the author's permission (email, 2026-10-19), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.