DevGizmo
DevGizmo'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 @DevGizmo86 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 reading-log corpus
stevenzamora1/reading-log: micromodules for bookshelf
- Reuse a worked example: the commit “Add extensible localization and Italian translations” (7 files · Lua).
- Answer from reading-log's real Lua source instead of memory (API design and specification).
- Where does reading-log handle “Add extensible localization and Italian translations”?
- What does micromodules do in reading-log?
Search the GitHub repository stevenzamora1/reading-log with XERJ (https://hub.xerj.org/corpus/stevenzamora1--reading-log). 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/stevenzamora1/reading-log reading-log && git -C reading-log checkout 365bb973d8106bb4740748fc5dcbebc74d528327 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./reading-log --url http://127.0.0.1:9200 --prefix reading-log --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: AGPL-3.0. Read it for the approach only, do not copy code.
corpus stevenzamora1--reading-log · API design and specification
Related corpora: koreader/koreader, yesrab/openUF
Search an OpenAPI spec from an agent · Case study: reference coding for agents
Selected work
stevenzamora1/reading-log
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/DevGizmo86)
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.