Yanis ♨️
Yanis ♨️'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 @yaniswav 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 TopicForge corpus
yaniswav/TopicForge: Read-only MCP server for ROS2 and DDS robotics. Let an AI agent inspect topics, DDS participants, QoS mismatches and rosbags. No write path
- Look up how TopicForge implements ai-agents, claude, cyclonedds, with answers cited to file and line.
- Reuse a worked example: the commit “shrink tools/list by a third and add restarts_by_name, s…” (24 files · Python).
- Answer from TopicForge's real Python source instead of memory (AI, prompts and agents).
- How does TopicForge implement ai-agents?
- What does src/topicforge do in TopicForge?
Search the GitHub repository yaniswav/TopicForge with XERJ (https://hub.xerj.org/corpus/yaniswav--topicforge). 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/yaniswav/TopicForge TopicForge && git -C TopicForge checkout b6acd96e7a073556f84a217542e5f862d4124d10 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./TopicForge --url http://127.0.0.1:9200 --prefix topicforge --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 yaniswav--topicforge · AI, prompts and agents
Related corpora: fastmcp, atoma-run--atoma, gbayerv26/memwall, elbayoumi/crewloom
AI search and retrieval with XERJ · Case study: reference coding for agents
Selected work
yaniswav/TopicForge
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/yaniswav)
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.