Large codebases are hard to review and even harder to understand. Codewalk grounds AI in your repository instead of guessing. AI code reviews work instantly on PRs—no indexing required. For deeper understanding, Codewalk builds a dependency graph and semantic index to answer questions with source-cited code and visualize blast radius before you refactor. Open source, self-hosted, and available as an MCP server, web app, or API.

Hey Product Hunt! 👋

I built Codewalk because I was frustrated with AI code review tools that only look at a diff. They don't understand your codebase, so they miss architectural impact, hidden dependencies, and often produce generic feedback.

Codewalk takes a different approach.

For code reviews, there's no repository indexing required. Just point it at a PR or diff, and it analyzes dependency impact, architectural risks, blast radius, and import cycles.

For repository understanding, Codewalk builds a dependency graph and semantic index, giving AI the context it needs to answer questions with source citations and help you navigate unfamiliar codebases.

It supports three core workflows:

🔍 Dependency-aware code reviews with blast radius, architectural risk, and import cycle detection

💬 Repository Q&A grounded in your code with source citations

🛠️ Code understanding & refactoring, showing what changes are affected before you modify them

You can run Codewalk as:

🖥️ An MCP server for Claude Code, GitHub Copilot, and other MCP clients
⚙️ A self-hosted API for CI and automation
🌐 A web app with a repository knowledge graph explorer

It's open source, self-hosted, and supports multiple languages through Tree-sitter.

The idea came from repeatedly inheriting unfamiliar codebases and wishing AI understood the architecture before giving advice instead of just reading changed lines.

I'd love your feedback:

Would you use it inside your IDE or in CI?
Which capability is most valuable: code review, repository understanding, or blast radius analysis?
What's missing before you'd trust it on your own repository?

Thanks for checking it out! Looking forward to hearing your thoughts.

Spun it up on a messy internal repo and the blast radius view actually made a gnarly refactor feel manageable. Love that it just works on PRs without waiting on an index.

@tahsinlimr Appreciate it!. Do try review I bet you will not disappoint

A Slack or GitHub bot that posts a quick "blast radius summary" comment on every PR would be incredibly useful for catching risky refactors before review even starts.