Explain /edit

[pcuci]

Problem

In the /edit workflow, continue responds with the code diff for the ^ + Shift + L'd code and often leaves me wondering why it's doing what it's doing.

To sort that out, I often accept the suggestion, then ask what it did. Then iterate.

Solution

What if we get 2 outputs:

• Continue Diff (today's behaviour), plus
• an additional response in chat explaining why this particular diff

One workaround is to ask it to /edit with comments, but then I have to delete the comments :-)

Ideally, I think the DX workflow should allow some fast iteration on the currently being looked at function/code(?) that shows for both the continue diff and the explanation to evolve on a sub-thread of sorts; don't know, thinking out loud here, mainly to point out the UX friction issue(?)