I think they even more so need deterministic feedback:
I tried an approach based on the following idea recently and it's amazing - Lint rules where the error messages contain an explanation on how to deal with the issue.
This looks pretty cool but I'd want to be able to setup a bunch of my own project specific code smells, so it's not just a few generic rules. Is that the approach you've taken?
Then for example you could write your own hook and convert existing code smell documentation which agents ignore into a format that works with the hook.
> but I'd want to be able to setup a bunch of my own project specific code smells
That's what I did; I did not use the library I linked to ~ It served only as an inspiration.
Instead, I let the agents create custom lint rules (using eslint, pylint, ...) and add custom coaching error messages based on where I want to take my codebase.
Garlef · · focus · HN ↗
I tried an approach based on the following idea recently and it's amazing - Lint rules where the error messages contain an explanation on how to deal with the issue.
<a href="https://habit-hooks.com/" rel="nofollow">https://habit-hooks.com/
I'm using it to foster IOSP (integration operation segregation principle) for example.
jcjmcclean · · focus · HN ↗
Then for example you could write your own hook and convert existing code smell documentation which agents ignore into a format that works with the hook.
Garlef · · focus · HN ↗
That's what I did; I did not use the library I linked to ~ It served only as an inspiration.
Instead, I let the agents create custom lint rules (using eslint, pylint, ...) and add custom coaching error messages based on where I want to take my codebase.
jcjmcclean · · focus · HN ↗