repo-scanner

To extract repository metadata and detect domain boundaries without reading source code, run a scan to infer domains like api, frontend, and backend from directory structures and file patterns. The scan produces a structured JSON report for assimilation planning.

Framework detection for assimilation prep identifies frameworks and tooling by analyzing configuration files and dependencies rather than source code. It generates a structured scan payload that informs subsequent pattern extraction and integration steps across common language ecosystems.

To generate a structured scan report mapping repository characteristics, run the scan to identify detected frameworks, domain boundaries, and project traits. The report is output as a JSON file at .github/temp/scan-report.json to inform integration planning.

Yes, the repository scanner enforces browse- and size-related rules when analyzing directory structures and file patterns. This ensures the scan extracts metadata and detects domains efficiently without reading all source code.

Yes, you can use repository scanning to infer domains like services and modules across common language ecosystems. The scan analyzes directory structures and file patterns to discover domain boundaries and generate a structured metadata report.

The best way to prepare a repository for pattern extraction and integration is to generate a scan payload that highlights detected frameworks and domain boundaries. This structured report provides the necessary metadata to inform subsequent assimilation planning.