[Feature]: More customizable commit message template and support for Perforce VCS

Description

💬 Discuss and agree about design before contribution

I am part of the Murex organization, we have a bit of time this summer, and we would like to contribute to your project. We want to extend it with the following features:

• More possibilities to customize the commit message itself: to include footers, a "Why" body header, and more details in the body (ex: we want to use it for code katas with TCR, we'd like to ask the AI to give us the list of named baby steps that the trainees used)
• Support for Perforce because most Murex developers rely on this VCS

To avoid rework, I would like to start a conversation to get your feedback about the proposed features and design before we send pull request.

Suggested Solution

• Commit customization: We have been thinking of a more advanced template with named sections that could be provided by custom prompts or by command line options
• Perforce VCS: obviously not all features will be supported. We could create an abstraction for the different VCS and let the tool switch to Perforce with an option, or a configuration. Another way would be to make the tool VCS agnostic, move all git commands out of the tool, and create shell wrappers to give it the diff through stdin, receive the message from stdout, and commit. I'm not sure how this would work with githook or github actions though.

Alternatives

We could start from another tool (ex aicommits)
We could build something from scratch ourselves

Additional Context

We also plan to use the tool on our own internal RAG. I'm not sure what impact will this have yet.

No files, tests, or entry points are identified. Start by mapping the existing commit-message generation and Git integration, then clarify the design and scope for customizable templates and Perforce support with maintainers. Done requires an agreed design and bounded implementation plan before contribution.