LAB: Improving The Git Commit Message
In the last session we used Gemini CLI to create a commit message for us, but the prompting process took longer than just writing the message ourselves. Do we have to do this every time we need a commit message? Hopefully not, it's too much work.
The ideal solution to this would be to have a stored prompt, something like create a git commit message and use git state and git diff to do it. add detail and emoji. That would be nice, wouldn't it? Unfortunately, at the time of this writing, that's not possible with Gemini CLI, however that is likely to change at a later time.
That's why we're going to use Copilot for this lab. While we're at it, we're going to prepare our store for the wilds of the open source world. If you want to use Gemini, feel free.
Step 1: Adding a README
Every project should have a README that explains what it is, what it requires to run, and how to run it. If your project will be open source, this README represents everything about it, which is one place AI can really help.
Open up Copilot and flip in to Agent mode. I'm using Claude Sonnet once again, but use whichever LLM you like: