gsc-cli

The code in http://github.com/gitsense/gsc-cli contains over 300 go files and I would say 90% were one shots. I can even prove that they are AI generated since I attribute the AI in each file, as shown in the example below: https://github.com/gitsense/gsc-cli/blob/main/internal/cli/r... Since I don't know go, I can't say which is the best. I am also sure they would not live up to a go experts expectations. I just know that since I don't know go, I would not have been able to create the tool. I can also prove that you can easily maintain AI generated code since I have been expanding and evolving it for over 6 months with pretty much no issues.

I am working on solving the AI Code Provenance problem and I believe my repos may be the first that provides AI code provenance. See the following example: https://github.com/gitsense/gsc-cli/blob/main/internal/cli/r... Notice how the code block header attributes the model. The UUID can be traced to the conversation so everybody can tell exactly how the code came about. For this to work though, you need to use my chat app as it ensures you can't tamper with things if you are truly serious about AI code provenance. I also have a lot more human-focused method which is part of my CLI tool. https://github.com/gitsense/gsc-cli I am currently looking at making pi (https://github.com/earendil-works/pi) support AI code provenance, but for now if you want a more structured way to capture what you have done in an agent session that can be used in c