Your codebase already wrote the rulebook.

Tell us the rules your team keeps enforcing by hand, and we write custom static analysis rules for the ones generic linters don’t know.

How it works.

From your own fixes: We read the fixes your team keeps making and write each rule down with you before automating it.
Tested both ways: Each rule is tried on code it should catch and on code that only looks similar, so it flags the defect and not its neighbours.
In your CI: We set the rules up in your CI, so a change that breaks one is stopped before it merges. A team that writes its own adds them as repository rules, which slopcop check evaluates beside the hosted ones.