Luke Roy
Luke Roy'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 @Luke-Roy-IBM 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 CodeEngine corpus
IBM/CodeEngine: Samples for using Code Engine
- Look up how CodeEngine implements ibm-cloud, code-engine, ibm-cloud-code-engine, with answers cited to file and line.
- Reuse a worked example: the commit “Clef on Fleets” (8 files · Python).
- Answer from CodeEngine's real Python source instead of memory (Operations and SRE).
- Where does CodeEngine handle “Clef on Fleets”?
- How does CodeEngine implement ibm-cloud?
- What does serverless-fleets do in CodeEngine?
Search the GitHub repository IBM/CodeEngine with XERJ (https://hub.xerj.org/corpus/ibm--codeengine). 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/IBM/CodeEngine CodeEngine && git -C CodeEngine checkout f4ccdfb9264ce3e1869b20723ae0b5644b345e43 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./CodeEngine --url http://127.0.0.1:9200 --prefix codeengine --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 ibm--codeengine · Operations and SRE
Related corpora: cloud-custodian, cloudevents-spec, 2FastLabs/agent-squad, oddbit/shrtnr
Operational intelligence with XERJ · Case study: reference coding for agents
Selected work
IBM/CodeEngine
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/Luke-Roy-IBM)
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.