Alison Alva commented on issue #26795 at Glasgow Haskell Compiler / GHC

Alison Alva
2026-01-19T02:44:38Z

@simonpj I implemented claude into personal Ci/CD lines in the form of generalist style guide and functionality checking, but realized it was a waste of server computing power when I could just add that exact code to my pre-commit hooks in git and get the same feedback faster. I do believe there is potentially a lot of value in adding validation and formatting checks with an LLM into the line somewhere, and when done correctly it doesn't need to consume a lot of processing power to purely sanity check commits.

I also experimented with adding claude 'closed loop' fixes as are being suggested here and most of them were fine, but I felt like the difference between most and all is too large of a chasm to let an LLM roam free in my code base; it created unexpected behaviors and drift in the experimental branch. I wouldn't suggest letting anything into a codebase that isn't viewed by a human at some point. If you would like evidence as to why, I suggest running these closed loop tests locally on any repo to watch what happens over time.

Looking at the Claude in Gitlab docs it says to use an API key, not a subscription? I believe that using a subscription in a pipeline is a direct violation of their ToS?