Every project has that moment before a commit where you think:
"Did I accidentally make this function too complex?"
"Is this file getting out of hand?"
"Did this class just become impossible to maintain?"
Most of the tools I used were excellent at catching syntax errors, formatting, or linting issues—but I wanted something that focused on code maintainability.
So over the past few weeks, I built Scrut.
Scrut is a lightweight, Git-aware Python code review CLI that analyzes your changed Python files using Python's built-in AST and highlights maintainability issues before they reach a pull request.
Current checks include:
Excessive function parameters
Deep nesting
Oversized functions
Large classes
Large files
It's intentionally simple. No heavy setup. No IDE required. Just run it inside a Git repository and get a quick review report.
📦 GitHub:
https://github.com/mukundzha/scrut
This is the very first public release, so I'm not claiming it's perfect.
What I'm really looking for is honest feedback from developers who write Python every day.
If you had a tool like this in your workflow:
What rule would you want first?
What would make you actually keep using it?
What feels unnecessary?
Every comment, bug report, and suggestion will directly shape the next version.
I'd genuinely appreciate your thoughts.
Top comments (0)