→ Don’t use new Date() directly. Inject a Clock. → This code is duplicated. → We don’t use lodash here.
Feels like we’re doing reviews on repeat in 2025.
That’s exactly why we built one of the most used features in Kodus: Kody Rules.
Team rules, your way, right inside the PR flow.
And the best part?
Kody learns from your team’s reviews.
It watches the comments you leave on PRs and starts suggesting those same things on the next ones.
No config upfront. No model training.
I recorded a quick video showing one of the rules we use: https://youtu.be/0J4TtooYDHU
→ “Avoid using new Date() directly in services. Inject the Clock.”
Simple, but it prevents annoying bugs, saves repetitive back-and-forth, and keeps standards in place without anyone having to remember them.
If you could automate just ONE comment you keep repeating in reviews, what would it be?
edvaldodfreitas•8mo ago
→ Don’t use new Date() directly. Inject a Clock. → This code is duplicated. → We don’t use lodash here.
Feels like we’re doing reviews on repeat in 2025.
That’s exactly why we built one of the most used features in Kodus: Kody Rules.
Team rules, your way, right inside the PR flow.
And the best part?
Kody learns from your team’s reviews.
It watches the comments you leave on PRs and starts suggesting those same things on the next ones.
No config upfront. No model training.
I recorded a quick video showing one of the rules we use: https://youtu.be/0J4TtooYDHU
→ “Avoid using new Date() directly in services. Inject the Clock.”
Simple, but it prevents annoying bugs, saves repetitive back-and-forth, and keeps standards in place without anyone having to remember them.
If you could automate just ONE comment you keep repeating in reviews, what would it be?