This might not be exactly what you were asking, but I found it to work well as the means to end with the best possible (given current knowledge) outcome, includ

This might not be exactly what you were asking, but I found it to work well as the means to end with the best possible (given current knowledge) outcome, including considerations such as avoiding code that is too smart, or otherwise justifying and documenting it well. Good commit messages. Why did I do what I did? How does it serve the end goal? What key decisions did I make? What were the trade-offs? What are the alternatives? If I can't justify the commit, I can improve—and by doing this exercise, I will know where. Ask reviewers to also review your commit messages. They might find gaps you missed, and it will help them in their code review.