Actually this is somewhat already done in a quite clever way by the product CodeScene by Empear (https://empear.com/ https://empear.com/). This tool looks at th

Actually this is somewhat already done in a quite clever way by the product CodeScene by Empear (https://empear.com/ https://empear.com/). This tool looks at the history of files in a repo and detects a lot of things such as: * Correlation between files (we always seem to change b.cs when we change a.cs) * We have lost knowledge in the team, file a.cs was 85% created by developer X who has now quit. * A certain file is often modified (indicating too many responsibilities, and thus "bad code"). and so on. More details: https://empear.com/blog/software-revolution-part1/ https://empear.com/blog/software-revolution-part1/