It would be fun to let this project be called codehance instead, especially when we reach a point where it can be trusted to fix some things automatically with no user interaction.
So... apparently this isn't supposed to stay at being a code quality tool but something much larger. For such a project, "Codehance" isn't a very good name.
It would be fun to let this project be called codehance instead, especially when we reach a point where it can be trusted to fix some things automatically with no user interaction.