Kody from Kodus

😎

Create rules that reference real files in your codebase Generic rules like “follow good naming conventions” rarely help. Every team already has real patterns in the repo: service templates, route configs, API contracts, error handling styles. With file references, Kody Rules can point directly to those files and use them as the source of truth. You can reference files like this: Create rules that reference real files in your codebase Generic rules like “follow good naming conventions” rarely help much. Every team already has concrete patterns in the repo: service templates, route configs, API contracts, error handling styles. With file references, your Kody Rules can point directly to those files and use them as the source of truth. How it works When writing a rule, you can reference files using two syntaxes: @file:path/to/file.ts → reference a file in the same repository @repo:org/project → reference a file in another repository When the rule is saved, Kody resolves the reference, fetches the file contents, and injects them into the review context. The rule now has real code to compare against, not just a guideline. Examples Enforcing a service pattern You can reference a service template like src/services/userService.ts and check whether new services follow the same constructor structure, naming patterns, or error handling. Validating route registration If a PR adds new controller routes, the rule can verify they are registered in src/routes.json. Cross-repo API consistency Rules can also reference standards stored in another repository, such as an internal API conventions repo.

1000 stars on GitHub ⭐️ good signal we’re on the right track still building @kodustech

Want full control over what gets flagged? @kodustech is open source and the most customizable tool we tested. Excited to see how it performs in the online benchmark as more OSS repos adopt it.

Turn your PR history into review rules Most teams have been doing code reviews for months, sometimes years. That means your repo already contains a lot of implicit rules. Comments like: “use early return here” “this endpoint needs validation” “don’t expose this field in the response” Those patterns can become actual Kody Rules automatically. How it works: Kody looks at the last 3 months of code review comments in your repository and searches for recurring feedback patterns. When it finds them, it converts those patterns into ready-to-use review rules. Step by step → Go to Code Review Settings → select your repository → Kody Rules → Click Generate Kody Rules → Kody scans the last 3 months of review history in that repo → It filters useful comments (ignores bots, short replies, etc.) and groups them by pattern → It generates up to 12 rules per cycle → A “Check Out New Rules” button appears so you can review everything before importing Nothing activates automatically. Only the rules you import will run during reviews. Why this is useful You don’t need to start from scratch. Kody extracts the patterns your team is already enforcing during reviews. Each rule also includes real examples from your codebase, so it reflects how your team actually works. The generator runs weekly. As review patterns evolve, new suggestions appear. If your team already has a decent review history but never configured rules, this is a great starting point. Run the generator, review the suggestions, import the ones that make sense, and in a few minutes your code review setup starts reflecting how your team actually reviews code. Generated rules behave like any other Kody Rule. You can edit them, change severity, or disable them anytime.

👀 $15–$25 per PR. You can use @kodustech OSS with Claude Opus, and it’ll cost less than 1/10 of the price. We have customers who process 1,000 PRs per week. That’s about $100k per month in review costs. In the long run, hiring a full-time engineer for code reviews is cheaper.

@Ed_dfreitas @oprimodev Não importa o tamanho, eu dou conta. Lá ele 😂

@oprimodev PRs pequenos quase sempre são melhores. (E você pode usar a @kodustech pra revisá-los 😉)

Na sua opinião, qual o tamanho aceitável pra um pull request?

conheçam o trabalho dos caras e comece a usar a kody da @kodustech o quanto antes, vai valer a pena cada centavo... afinal de contas é DE GRÁTIS coderabbit killer OBS: também é OSS github.com/kodustech/kodu…

A must-have card in the deck of any engineering team. cc @kodustech

We recently put together a hands-on benchmark of AI code review tools using real PRs from five open source projects. I dropped the link in the comments if you want to take a look.

é acho que não da pra ir pra prod ainda KKKK

The famous “we’ll fix it later” is the sentence that creates the most technical debt in a team. And in practice, that “later” almost never happens😓 👉 If the goal is to control how fast the debt grows, the PR is the best place to intervene. What helps in that moment is having a few simple review criteria: - Confirm that the change follows the standards the team already agreed on. - Question duplications, inconsistencies, and new dependencies before the merge. - Create a checklist, even a simple one, to guide whoever is reviewing. How does your team handle this in the day to day?

🧡

Last week we hosted our first hackathon. 🧡 It was an intense weekend, but also a really fun one. We spent a good amount of time talking about AI and the current state of the tech industry. Then we jumped into the hands-on part. The challenge was to build a functional MVP that solved a real problem. We ended up with some great projects, and a few teams even decided to keep working on theirs after the event. Now we’re looking forward to the next one, the energy was so good that we want to do this more often.

@ducaswtf @gamalinosqui 🧡

joguei o coelho fora. agora o uirepo.xyz é 100% @kodustech cc @gamalinosqui

@sahil_builds 🙌

@kodustech congo 🎉🎉

This week we hit 700 stars on GitHub 🧡

@jetfemartins @R4kashy Isso aí, essa parte deixa comigo

@R4kashy Com todo respeito patrão, viajou Usos diferentes, contextos diferentes e resultados totalmente diferentes A impressão que eu tenho é que pra fazer código a IA só cospe um ho horse Agora conferir código é outros 500 Tanto que tem ferramentas só pra isso, como a @kodustech

O cara reclama de vibecoded e usa chatgpt pra fazer code Review KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK, essa rapaziada da bolha dev é incrível memo