Hacker News new | ask | show | jobs
by 8bitsout 46 days ago
That's a pretty neat idea. What does "map technical debt, agent readiness, code complexity" look like? How does that get done?
1 comments

we do a very comprehensive scan in multiple dimensions: git blame history, llm passes over every file and a tree-sitter analysis for cognitive complexity. We bring our opinionated approach for tools (do you have linters, CI/CD, static typing, agent docs) and score each aspect. We also create your architecture diagrams with our secret agent sauce, and map technical debt on each level of the C4 hierarchy.
Thanks for sharing :)