Ouro Ouroboros

gather

Overview

Scans the repository to detect technologies and seed Ouro knowledge files. Depending on flags, it inspects package.json files, Deno import graphs, Ruby Gemfiles, and Python requirement files. The command enriches .ouro/technologies/, updates .ouro/technologies/MAP.md, and prepares package metadata for downstream tooling.

Usage

ouro gather [--deno] [--ruby] [--python] [--agent-model <model>] [--codex-model <model>]

Key Options

  • --deno – Derive dependencies from Deno import specifiers and import maps using Codex assistance.
  • --ruby – Parse Gemfile, Gemfile.lock, and .gemspec files to record Ruby gems.
  • --python – Scan requirements.txt, pyproject.toml, setup.py, and Pipfile.lock for Python packages.
  • --agent-model <model> – Override the model used for docs map summarisation.
  • --codex-model <model> – Override Codex when analysing Deno import graphs.

Inputs & Outputs

  • Inputs: repository source files and manifest files; optional flags controlling language support.
  • Outputs: updates .ouro/technologies/MAP.md, fetches READMEs for npm packages, records curated docs under .ouro/technologies/, and logs progress in the terminal via spinners.

When to Use

  • Before running create, map, or automation flows that rely on an accurate technology catalogue.
  • After adding dependencies so the knowledge base reflects the new stack.

Follow-up Checklist

  • Inspect .ouro/technologies/ for any missing or redundant entries.
  • Run ouro map to align the ontology with the updated technology list.