I built a fun side project ? a Go static analyzer that finds code smells. Then I made it work with Claude Code via MCP (Model Context Protocol). Now AI can roast your Go code automatically.

Repo: github.com/aqylsoft/godepvis

The Problem I Didn't Know I Had

You know that moment when you're reviewing a PR and you see a 200-line function? Or a method with 9 parameters? Or someone using context.Background() right next to a perfectly good ctx ?

These things aren't bugs. They compile fine. Tests pass. But they make you go "hmm" and reach for the comment button.

I wanted a tool that catches these patterns automatically. Not to replace code review ? but to handle the boring "hey, this function is too long" comments so humans can focus on actual logic.

Golangci-lint is great, but configuring it to catch architectural smells requires yoga-level flexibility.…