CodeTrace-AI
Ground your AI coding agent in your actual codebase
12 followers
Ground your AI coding agent in your actual codebase
12 followers
CodeTrace-AI is an autonomous engineering intelligence platform that understands entire repositories through structural analysis, semantic search, dependency mapping, call graphs, and AI reasoning.
A dependency map for test coverage would be a great addition, showing which unit and integration tests actually exercise each module or function call chain. Right now I can see what calls what, but not what gets validated, which makes it harder to spot untested critical paths before refactoring. Could your AI flag functions with no direct or indirect test coverage and suggest missing test cases for high-risk code?
@nuriyebavatll2 Sorry for late reply.
Thanks so much for this feedback! You hit the nail on the head regarding one of the biggest anxieties developers face with AI-assisted refactoring: "I know what calls this, but will a test catch it if something breaks?"
Mapping unit and integration tests directly onto the dependency graph is a natural extension of our blast-radius engine. We’re actively exploring an overlay where CodeTrace connects test suites to execution paths, highlighting "blind spots" (critical, high-blast-radius functions with zero direct/indirect test coverage) and prompting the AI agent to draft targeted tests before allowing refactors.
This is definitely going straight to the top of our roadmap. Would love to have you in our Slack, GitHub if you’d like early access to test this when we drop the beta! 🚀
would love to see a way to drop in an issue or bug report and have it auto-trace the failing call path back to recent commits that touched those files, basically a blame + impact overlay. that would save so much time compared to hunting through git history manually
@melihacelercmv Sorry for late reply.
This is a brilliant idea! Triage and root-cause analysis are huge time sinks, especially when a bug touches multiple layers across several recent commits.
Having an Issue/Stack Trace → Call Path → Git Blame + Blast Radius pipeline fits right into CodeTrace's architecture. Since we already have the local graph of your codebase, feeding in an error log or issue and correlating the execution path with recent commit deltas (git log/blame) to pinpoint the exact suspect commit is completely doable — and 100% local!
Adding this "Time-Travel Debugging / Blame Overlay" to our roadmap. Thanks for the awesome suggestion, and feel free to jump into our GitHub/community if you'd like to share sample workflows you'd want supported! 🔥
GitHub, Slack