kumoss
Kumoss turns natural-language requests into compliant, plan-validated Terraform/OpenTofu pull requests - with drift correction, policy gates, and human review. Multicloud, bring-your-own LLM
What XERJ indexed
Snapshot
The whole repository at commit 316df4f5e2 (2026-10-15). main is 87 commits ahead.
Selected work
“add VMware vSphere provider”. 52 files, 1,079 lines in core/prompts, core/tests, core/src.
Licence
The repository
LICENSE file checked at the pinned commit; the author agreed to inclusion.
The XERJ corpus
The author agreed by email on 2026-10-27. Same terms as the repository. Answers name the repo, the commit and the file:line.
selected for the XERJ Corpus Hublicence clearedsuggested use: adapt with attribution
ai-agentsawsazurecloud-governancedevopsgcpiacinfrastructure-as-code
Example questions
- How does kumoss implement ai-agents?
- Where does kumoss handle “add VMware vSphere provider”?
- What does core/prompts do in kumoss?
Inside the indexed corpus
- 1,058 files, 155.0 MB in total, about 150.0 KB per file.
- The selected commit changed 52 of those files (4.9%).
- Languages by size: Python 62.6%, TypeScript 29.5%, CSS 3.8%, Jinja 3.4%, Dockerfile 0.4%.
- On GitHub since 2026-05-06, last push 2026-10-30, 982 commits on main.
- The pin is 87 commits behind main; the corpus answers from the pinned code, not the newest.
Licence on GitHub and in the corpus
GitHub reported Apache-2.0 for InditexTech/kumoss on 2026-10-31, and the LICENSE file at commit 316df4f5e2 was reviewed as Apache-2.0. They match, so answers from this corpus carry the same terms as the live repository.
Contributors
Luis Valerio (@Luisivg) has 1 selected repository on the hub.
Using XERJ with kumoss
- Search text across Kubernetes pod logs from many pods kumoss is tagged kubernetes on GitHub.
- Find every place a config key is set in a repo
- Index a reference library for a coding agent
- ripgrep vs a code index for coding agents: 30 tasks
The prompt
Paste it into your AI agent. It clones InditexTech/kumoss at the pinned commit and indexes it on your machine.
Search the GitHub repository InditexTech/kumoss with XERJ (https://hub.xerj.org/corpus/inditextech--kumoss). 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/InditexTech/kumoss kumoss && git -C kumoss checkout 316df4f5e26fa828acf40ad4ab095ebbd1872ad5 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./kumoss --url http://127.0.0.1:9200 --prefix kumoss --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.
Related
Luis ValerioOperations and SRE corporacheckovcloud-custodiancrossplanedcotecnologia/kubescopetotoshko88/Cloud_Architecturen8n-io/terraform-aws-n8n
Stats: GitHub API, fetched 2026-10-31. Snapshot: the git tree at the pinned commit. Selected work and consent: the XERJ registry.