nancy

Corpus Hub contributor since 2026-10-20

nancy'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.

1corpus

1selected commit

4files

585lines

★ 54,114GitHub stars on repo

Totals across every corpus @nancy6547 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 chrome-devtools-mcp corpus

ChromeDevTools/chrome-devtools-mcp: Chrome DevTools for coding agents

Look up how chrome-devtools-mcp implements mcp-server, puppeteer, chrome-devtools, with answers cited to file and line.
Reuse a worked example: the commit “describe Map, Set, function, DOM node, symbol and cycl…” (4 files · TypeScript).
Answer from chrome-devtools-mcp's real TypeScript source instead of memory (AI, prompts and agents).

Example questions

How does chrome-devtools-mcp implement mcp-server?
What does src/formatters do in chrome-devtools-mcp?

Paste it into your AI agent. It clones the repo at the pinned commit and indexes it on your machine.

Search the GitHub repository ChromeDevTools/chrome-devtools-mcp with XERJ (https://hub.xerj.org/corpus/chromedevtools--chrome-devtools-mcp).
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/ChromeDevTools/chrome-devtools-mcp chrome-devtools-mcp && git -C chrome-devtools-mcp checkout 968e4e5c504227b94166456d6039b30b1cf0670b
3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data
4. xerj autoindex ./chrome-devtools-mcp --url http://127.0.0.1:9200 --prefix chrome-devtools-mcp --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: Apache-2.0. Keep the copyright notice and credit the authors.

corpus chromedevtools--chrome-devtools-mcp · AI, prompts and agents
Related corpora: atoma-run--atoma, jose-js, heygen-com/hyperframes, oddbit/shrtnr
AI search and retrieval with XERJ · Case study: reference coding for agents

Selected work

GitHub ★ 54,114

ChromeDevTools/chrome-devtools-mcp

968e4e5c50 fix(console): describe Map, Set, function, DOM node, symbol and cycl…

selected commit: 4 files · 585 lines · TypeScript · src/formatters, tests

The corpus is the whole repository at the pinned commit, not only the files of the selected commit.

selected · in licence reviewcorpus chromedevtools--chrome-devtools-mcpAIApache-2.0mcp-serverpuppeteerchrome-devtoolsbrowserchromedebugging agreed 2026-10-20

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.

[![XERJ Corpus Hub contributor](https://hub.xerj.org/contributors/nancy6547/badge.svg)](https://hub.xerj.org/contributors/nancy6547)

Included with the author's permission (email, 2026-10-20), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.