itcharlie

In my previous blogpost I briefly discussed the use of Gemini Cli on a Perl dancer application to analyze its codebase. The next step is to generate a product requirement document. Why is this important ? well I had a bad experience with Gemini on another application where I allowed it to roam free "YOLO" mode and it basically started fixing all the problem areas one after another for about an hour or so until my free trial of Google Gemini expired for the day. This resulted into a completely rewritten application that was not able to run due to so many different errors. The cool thing is that I had version control so a good old "git reset --hard Head" cleared up my project and I could start over again.

Ok so back to the product requirement document, this document basically outlines the steps needed to resolve all the recommendations made by Gemini Ai during its code analysis. This means that you now have a clear path for AI to follow and you can essentially continue where you left off just in case you run out of free AI tokens for the day. Also make sure that you have a project that is under version control so you can commit changes as they occur after testing. Here is an example of the PRD.md file from my github repository.