Some languages like RUst you mentioned, have a clear tag that says "this is a test," but others do not, so the tool has to guess from file names and ends up missing some and skipping too much.
Also as I mentioned on the answer below, sometimes you actually do want to see the repeats inside tests, or normal code repeats on purpose too. So I am leaning toward letting users wave off one specific case by hand instead of skipping everything blindly.
What I use for: I use for identifying duplicated code. It is deterministic, doesn't use AI, offline, runs from CLI and is super fast (and free).
What I dislike: I won't say it I dislike, but it is not a tool that does all the jobs of a code review. For instance, it doesn't flag security issues. It is superfocused on code duplication (it performs better than Sonar for this use case) and is specifically useful for large codebases. Disclaimer: I am one of the collaborators, so take it with a grain of salt https://github.com/Rafaelpta/dupehound
This is a pattern I encourage - the AI might not be reliable, but with coaching, it can produce reliable tools. `colordiff` was causing issues with `less` when I was looking at diffs (character encoding issues I think), and when I asked Kimi K2.6 what to do, it built me a rust command-line diff tool in one shot that I've been using ever since (it even downloaded rust, wrote the tool, and compiled it).
What is an AI powered content engine then?