I recently reviewed some code written by a non-engineer using Cursor's vibe coding. It was full of dead code and patchwork logic. Vibe coding can build a working prototype, but maintaining it? That's another story.
So I built a GitHub App that audits your Python codebase. It reviews PRs and runs weekly scans on the entire repo, catching complex functions, dead code, and duplicates. When it finds issues, it posts comments and Issues with concrete suggestions.
Comments
I recently reviewed some code written by a non-engineer using Cursor's vibe coding. It was full of dead code and patchwork logic. Vibe coding can build a working prototype, but maintaining it? That's another story.
So I built a GitHub App that audits your Python codebase. It reviews PRs and runs weekly scans on the entire repo, catching complex functions, dead code, and duplicates. When it finds issues, it posts comments and Issues with concrete suggestions.
It's powered by pyscn (https://github.com/ludo-technologies/pyscn), a static analyzer I open-sourced a few months ago.
Happy to answer questions.