I just thought about it a bit more and removed this `averaging` feature :) While it is possible to do such things, I couldn't find any proper use case for it. Using this feature would be gambling: you would need to be sure the codestyle is already almost ok, instead you could suddenly get something wrong.

It is far better to detect the codestyle manually and then save it to a config. This way you could revisit it and change the things you don't like.

So, as this feature is just a shortcut for this, I now see that is shouldn't bloat the main codebase :)