That does seem useful. I guess it's the name that confuses me.

i’m reading the syntax draft , and found this:

If the first word appearing in the title is “COMMENT”, the headline will be considered as “commented”. Case is significant.

and indeed, if i add COMMENT as the first word of the title, it gets the org-special-keyword face.

But what does “commented” mean?

By default, the report ignores commented (see Comment lines) and archived (see Internal archiving) entries. You can override this by
setting ‘org-agenda-skip-comment-trees’ and
‘org-agenda-skip-archived-trees’ to ‘nil’.

Finally, a ‘COMMENT’ keyword at the beginning of an entry, but after
any other keyword or priority cookie, comments out the entire subtree.
In this case, the subtree is not exported and no code block within it is executed either(1).

You could try adding this to your .git/config file:

[diff "org"]
xfuncname = "^\+ +.$"

Then add this to .git/info/attributes:

*.org diff=org

I don't often look at git diffs of my Org files, but I added that to my Org files' git repo years ago, and it seems to help.

This is excellent, thank you