MadhusudhanT
MadhusudhanT'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 @madhusudhan-rgb 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 ForgeHQ corpus
ForgeBuilds/ForgeHQ: Main HQ
- Look up how ForgeHQ implements hq, main, website, with answers cited to file and line.
- Reuse a worked example: the commit “Changes : changes to the legal papers” (20 files · TypeScript).
- Answer from ForgeHQ's real TypeScript source instead of memory (Web and frontend platform).
- Where does ForgeHQ handle “Changes : changes to the legal papers”?
- How does ForgeHQ implement hq?
- What does components do in ForgeHQ?
Search the GitHub repository ForgeBuilds/ForgeHQ with XERJ (https://hub.xerj.org/corpus/forgebuilds--forgehq). 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/ForgeBuilds/ForgeHQ ForgeHQ && git -C ForgeHQ checkout c8b27951ac3e60388700c6ba6568d473e0bbcd11 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./ForgeHQ --url http://127.0.0.1:9200 --prefix forgehq --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 forgebuilds--forgehq · Web and frontend platform
Related corpora: oss-attribution-builder, astro-docs, airqo-platform/AirQo-frontend, Taimkellizy/portfolio
Case study: reference coding for agents
Selected work
ForgeBuilds/ForgeHQ
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/madhusudhan-rgb)
Included with the author's permission (email, 2026-10-18), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.