Osama Abbas
Osama Abbas'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 @OsamaAbbas 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 bytenode corpus
bytenode/bytenode: A minimalist bytecode compiler for Node.js
- Look up how bytenode implements nodejs, bytecode, v8, with answers cited to file and line.
- Reuse a worked example: the commit “add optional source maps” (9 files · JavaScript, TypeScript).
- Answer from bytenode's real JavaScript source instead of memory (API design and specification).
- Where does bytenode handle “add optional source maps”?
- How does bytenode implement nodejs?
- What does lib do in bytenode?
Search the GitHub repository bytenode/bytenode with XERJ (https://hub.xerj.org/corpus/bytenode--bytenode). 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/bytenode/bytenode bytenode && git -C bytenode checkout b3f751b7be0f472edf784686eef18240d6160b88 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./bytenode --url http://127.0.0.1:9200 --prefix bytenode --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: MIT. Keep the copyright notice and credit the authors.
corpus bytenode--bytenode · API design and specification
Related corpora: markdownlint, jsdom, amir1387aht/MicroCS, PySudo/QuantoScript
Search an OpenAPI spec from an agent · Case study: reference coding for agents
Selected work
bytenode/bytenode
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/OsamaAbbas)
Included with the author's permission (email, 2026-10-24), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.