Comment by alok-g

This is something I have been looking for.

I agree with a lot of comments here saying that the "conversation that generates the code" is often not meaningful once the code is there. It is however important to me as development history. Commit messages, meanwhile, are not the right places to hold this conversation.

As of now:

1. I save the conversations as "Prompt ###-XX.md" files into a 'completed prompts' folder within the repository and cite "Prompt ###" in the commit message.

2. I explicitly have the coding agent explain the decisions from the conversations in the generated code/artifacts.