For AI agents: the complete documentation index is available at https://docs.flezise.com/llms.txt, the full documentation bundle is available at https://docs.flezise.com/llms-full.txt, and this page is available as Markdown at https://docs.flezise.com/knowledge-base/repository-scan.md.
Docs

Repository scan

A repository scan indexes the project's connected repository into the knowledge base. It clones the repository, walks every source file, builds AST and module summaries, detects the tech stack, and writes the results to the code graph. When the scan finishes it triggers the as-is baseline run, which generates reverse-engineered documentation from the indexed content.

Running a scan

Open Settings in the project sidebar, then select the General tab. Enter or confirm the repository URL in the Repositories section, then click the scan icon to the right of the URL field. The icon spins while the scan runs.

When the scan completes, a results panel appears below the repository field showing what was indexed.

Note

Multi-repository support is not yet available. The Add button in the Repositories section is disabled.

What the scanner does

  1. Clone or pull: fetches the repository into a working directory. For local repos it checks out the branch with the most recent commit.
  2. File classification and AST extraction: walks every source file, classifies it by language, and extracts AST metadata (declarations, imports, structure).
  3. Module summaries: generates one-line and module-level summaries for directories and files.
  4. Tech-stack detection: identifies languages, frameworks, and tooling from file patterns.
  5. Code graph indexing: writes the classified files and their relationships to the code graph, making them available for vector and keyword search.
  6. Codebase-audit artifact: creates or updates a codebase-audit artifact with the scan findings.
  7. As-is post-scan hook: triggers the as-is baseline run so reverse-engineered documentation is generated from the freshly indexed content.

Next steps