repo-research

To generate repository architecture documentation and Mermaid diagrams, provide the target codebase path or URL. The tool analyzes the codebase and outputs a complete research/ folder containing 10 structured documents with 50+ diagrams covering workflows, algorithms, configuration, and deployment.

Yes, you can reverse-engineer microservices codebases to understand workflows and algorithms. The analysis applies across repo types from monoliths to microservices, reading README.md and CLAUDE.md files to tailor the extracted architectural research documents.

The best way to onboard new engineers to a complex codebase is generating structured research docs. This produces 10 comprehensive documents explaining architecture, frontend, testing, and limitations, providing a complete end-to-end study of the repository.

Yes, repository analysis always generates all 10 research documents together without partial output. This ensures a complete end-to-end structural analysis, covering architecture, configuration, deployment, testing, limitations, and SaaS opportunities.

To identify SaaS opportunities when analyzing a codebase, the research process extracts key files and studies structural limitations. It automatically outputs a dedicated document evaluating potential SaaS opportunities within the analyzed repository.

Yes, you can document an undocumented monolith repository without manually reading every file. The analysis reads core configuration files, extracts key source files, and builds 10 structured documents with Mermaid diagrams covering the complete architecture automatically.