Looks interesting. In my experience the way current coding agents behave is - they make a change, then rely on linter to highlight errors due to the change. Once linter errors are highlighted, they try to fix them.

Providing access to something like this via mcp might help these coding agents plan better and limit or atleast understand the blast radius for refactors.

Will try.