I like the idea of "patch golf". If only people would at least do a diff before they commit to spot gratuitous reformatting or accidental changes :-(
That's the exact reason I thought of it [1]. With "large" code base, every character impacts the project, patch size becomes a skill. That said, it's so tempting to fix multiple almost related things in one go.
[1] also, git surgically precise patch mindset helped too.
[1] I regularly nerdgasm at LibreOffice releases reading how many thousands LoC they removed from the code base.
ps: beside code golf, I think there should be a patch golf thing. Try the smallest changeset that fixes or add a feature.