Paulo Gomes
Paulo Gomes'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 @pjbgf 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 sha1cd corpus
pjbgf/sha1cd: SHA1 implementation with collision detection
- Look up how sha1cd implements collision-avoidance, collision-detection, go, with answers cited to file and line.
- Reuse a worked example: the commit “amd64: Add an AVX2 fallback for CPUs without SHA-NI” (6 files · Go).
- Answer from sha1cd's real Go source instead of memory (API design and specification).
- Where does sha1cd handle “amd64: Add an AVX2 fallback for CPUs without SHA-NI”?
- How does sha1cd implement collision-avoidance?
- What does test do in sha1cd?
Search the GitHub repository pjbgf/sha1cd with XERJ (https://hub.xerj.org/corpus/pjbgf--sha1cd). 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/pjbgf/sha1cd sha1cd && git -C sha1cd checkout aaee7155f94d0582f9147c34ac3d2bcd35b61c26 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./sha1cd --url http://127.0.0.1:9200 --prefix sha1cd --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 pjbgf--sha1cd · API design and specification
Related corpora: knox, coredns, shamaton/msgpack, arandu-io/arandu
Search an OpenAPI spec from an agent · Case study: reference coding for agents
Selected work
pjbgf/sha1cd
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/pjbgf)
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.