If you're just going to use it once, or if all usages have `[it=foobar]`, I don't think you'd do it.
I could imagine doing something like what you mention if I had moved code from another context, and I wanted to have a commit that shows plainly that it was moved verbatim. But then I'd make subsequent commit where I do the necessary substitution.
If you never pulled out code into its own separate function just in order to name some lines of code, you should give it a try. You can avoid a lot of comments and/or confusion by just structuring your code in a way that allows you to name lines of code as concepts and abstractions. No need for it to happen more than once for you to do so.
But I don't understand your point in bringing it up here.
> "It is not worth doing," she said, [it=foobar]
baz(it) = "$it is not worth doing"
baz("foobar")
`it` is neither a descriptive identifier, nor did I see a suggestion for what the function `baz` could be called to make it descriptive.
Spitballing:
"It is not worth doing," she said, [it=foobar].
We do this all the time in programming languages. Without introducing too much syntax, this is doable.