Maazin Shaikh
Maazin Shaikh'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 @maazin 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 Zipply corpus
maazin/Zipply: maazin/Zipply (TypeScript)
- Reuse a worked example: the commit “Fix a new Google Sheet being created on every log” (6 files · TypeScript).
- Answer from Zipply's real TypeScript source instead of memory (API design and specification).
- Where does Zipply handle “Fix a new Google Sheet being created on every log”?
- What does tests do in Zipply?
Search the GitHub repository maazin/Zipply with XERJ (https://hub.xerj.org/corpus/maazin--zipply). 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/maazin/Zipply Zipply && git -C Zipply checkout 2e2dc56a08751c09958431d48d343959eec1adc8 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./Zipply --url http://127.0.0.1:9200 --prefix zipply --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 maazin--zipply · API design and specification
Related corpora: redocly-cli, asyncapi-bindings, serverless-workflow-spec, json-api-spec
Search an OpenAPI spec from an agent · Case study: reference coding for agents
Selected work
maazin/Zipply
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/maazin)
Included with the author's permission (email, 2026-10-21), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.