Saif Ali
Saif Ali'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 @saifelyzal 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 zela corpus
nexusrun/zela: Zela is an open-source platform for deploying and managing Docker clusters, with a web dashboard, encrypted networking, monitoring, and MCP
- Reuse a worked example: the commit “added shared storage support” (36 files · Go, JavaScript).
- Answer from zela's real Go source instead of memory (Operations and SRE).
- Where does zela handle “added shared storage support”?
- What does internal/control do in zela?
Search the GitHub repository nexusrun/zela with XERJ (https://hub.xerj.org/corpus/nexusrun--zela). 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/nexusrun/zela zela && git -C zela checkout 0c96d138dc048773497d6b1324f9ed35db3f4772 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./zela --url http://127.0.0.1:9200 --prefix zela --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 nexusrun--zela · Operations and SRE
Related corpora: cdk8s, coroot, fluxcd-website, tldr-pages
Operational intelligence with XERJ · Case study: reference coding for agents
Selected work
nexusrun/zela
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/saifelyzal)
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.