← Back to context

Comment by jcjmcclean

16 hours ago

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.