Option to include successful prompts in commits

Goals accomplished:

  1. provides additional documentation and context, both for reviewing commits and historically;
  2. promotes honesty about developer contributions, e.g. for blame assignment, sharing best practices;
  3. enables code evolution at the prompt level (see: Taelin w serwisie X: „what if… I reimplement all of HVM… not in Rust, not in Haskell… but in plain English? no code, just .prompt files […]” / X);
  4. might be helpful for training next generations of models.

Possible approaches / formats:

  • As sections at the end of the commit message, e.g. with file names as headers.
    • Pro: (1), partially (2), (4). Con: (3), (2): hurts discoverability.
  • As edited-filename.prompt files.
    • Con: Doesn’t work with multi-file prompts.
  • As feature-name.prompt files.
    • Good fit for projects evolving through PRs rather than flat commits.

Looks like there isn’t much interest. I might try implementing this as an extension if I get some spare time.

This extension should be sufficient:
Built a Cursor Extension to save and share chat and composer history - Showcase - Cursor - Community Forum

Thanks!