ParthPoudyal
ParthPoudyal'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 @ParthPoudyal 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 Atlas corpus
ghostuf/Atlas: Atlas maps blast radius, maintainer health, and vulnerability reachability across your dependency graph, then dispatches AI agents to…
- Reuse a worked example: the commit “REFACTOR:” (26 files · Go).
- Answer from Atlas's real Go source instead of memory (AI, prompts and agents).
- Where does Atlas handle “REFACTOR:”?
- What does core do in Atlas?
Search the GitHub repository ghostuf/Atlas with XERJ (https://hub.xerj.org/corpus/ghostuf--atlas). 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/ghostuf/Atlas Atlas && git -C Atlas checkout bbfa8c50dda4d4a9866aaf2237eed62e06c8bdcf 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./Atlas --url http://127.0.0.1:9200 --prefix atlas --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 ghostuf--atlas · AI, prompts and agents
Related corpora: atomic-agents, flagembedding, fabric, r2r-enforce
AI search and retrieval with XERJ · Case study: reference coding for agents
Selected work
ghostuf/Atlas
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/ParthPoudyal)
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.