Ivan Ramljak
Ivan Ramljak'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 @piqusy 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 murmur corpus
piqusy/murmur: Inline annotations for Neovim - leave instructions for AI agents directly on source lines
- Look up how murmur implements ai, annotations, code-review, with answers cited to file and line.
- Reuse a worked example: the commit “anchor murmurs to charwise visual selections” (3 files · Lua).
- Answer from murmur's real Lua source instead of memory (AI, prompts and agents).
- Where does murmur handle “anchor murmurs to charwise visual selections”?
- How does murmur implement ai?
- What does lua do in murmur?
Search the GitHub repository piqusy/murmur with XERJ (https://hub.xerj.org/corpus/piqusy--murmur). 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/piqusy/murmur murmur && git -C murmur checkout 9c393cb0271a58bbf11f1251b6b308a032ca3864 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./murmur --url http://127.0.0.1:9200 --prefix murmur --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 piqusy--murmur · AI, prompts and agents
Related corpora: annoy, guardrails, xeind/vallow.nvim, pakut2/wmc.nvim
AI search and retrieval with XERJ · Case study: reference coding for agents
Selected work
piqusy/murmur
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/piqusy)
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.