Perhaps by permuting your code the system could determine if there was anything that wasn't required to make the test pass and exclude it from the check-in. I

Perhaps by permuting your code the system could determine if there was anything that wasn't required to make the test pass and exclude it from the check-in. I often code three or four commits worth at once when on a roll and it's a pain doing multiple staged adds, stashes, tests, and commits to store each sub-change on its own. Having a tool to help with this would be great.