In the next section, we'll discuss libraries, both existing and possible, for storing these patterns/rules and making them easily usable in a dev workflow.
The rest is still unwritten...
This post is the 6th of a series on Refactor verification, investigating how to verify the correctness of refactors (or automating the human error away). All source code shown is on GitHub. Let me know if you found it useful on Twitter, happy refactoring! :—)