Repo Scanner

To catalog and prioritize GitHub repositories, provide a GitHub owner name to trigger a bulk GraphQL metadata fetch. The scan normalizes inputs, derives per-repo fields like category and stack, and outputs a pre-ranked Top 5 fleet catalog for downstream consumption.

Repository fleet management is the process of structuring all GitHub repos under an owner into a prioritized, machine-readable catalog with coded opportunities. You need it when managing large repository counts and requiring deterministic ranking to identify actionable targets for downstream automation.

You can scan GitHub repos in bulk using GraphQL by supplying an owner name in the aeon.yml var field. The tool fetches repository metadata in bulk, applies an opportunity taxonomy, and writes a persistent catalog to memory/topics/repos.md for reuse by other skills.

Yes, you can generate a machine-readable catalog of GitHub repositories by running a fleet scan. The tool produces a structured fleet with enforced taxonomy codes and deterministic ranking, writing the results to memory/topics/repos.md for direct consumption by downstream automation skills.

Yes, the repository scanning approach supports change-detection and delta reporting to keep the fleet relevant. It also includes agent-repo tagging features that maintain the accuracy of the persistent catalog over time as repositories evolve.

The best way to maintain a structured opportunity taxonomy across a large GitHub fleet is to use a scanning tool that enforces taxonomy codes and deterministic ranking. This ensures every repository receives consistent category, stack, and description fields for reliable downstream consumption.