Repowise · Codebase intelligence
doctoolchain / bausteinsicht
a more modern C4/Structurizr tool which let's you maintain a model of your architecture and sync it with your draw.io views
Does the health score find the bugs?
Repowise ranks every file by predicted defect risk. Of the 20 files it flags as riskiest, 20 (100%) actually needed a bug fix in the last 6 months — 4.3× better than picking files at random.
Languages
- go65.9%
- asciidoc18.2%
- markdown4.5%
- shell4.5%
- yaml3.6%
- json1.7%
- typescript1.1%
Key modules2
- go
test-report-generator
scripts/test-report-generator
- typescript
vscode-extension
vscode-extension
Code health
Full reportHow doctoolchain/bausteinsicht works
a more modern C4/Structurizr tool which let's you maintain a model of your architecture and sync it with your draw.io views This page is an auto-generated, always-fresh map of the doctoolchain/bausteinsicht repository, written primarily in Go. Repowise indexes the source, parses every symbol, computes a dependency graph, scores per-file code health from complexity, duplication, test coverage and churn, mines git history for hotspots and ownership, and lifts the resulting architectural decisions into a wiki you can read or query through MCP.
The codebase has 358 source files, 2,231 symbols, and 9 languages, structured as a monorepo with 2 packages. Git churn analysis flags 30 high-frequency files as hotspots — places where bugs, rewrites, and code review tend to concentrate. The dependency graph clusters into 130 tightly-coupled module communities.
Use the panels above to open the interactive dashboards, or connect this repo to your editor via the Repowise MCP server for grounded answers inside Claude, Cursor, or VS Code.