[numtel]

Definitely agreed. My workflow for a commit is always:

    git status
    git diff HEAD
    git add (usually -u)
    git commit

I catch so many mistakes checking the diff before committing. Just seeing the code in a different context helps things pop up.

[jononor]

git add -p is my default. Usually what I have been up to belongs in 2-3 separate commits, each with a good commit message. For example a bug found and fixed while developing a feature always goes in its own commit.