Author: Edvaldo Freitas
-
1.0.33 – Less noise in reviews, more clarity in configs
Improvements & New Features 🗑️ Delete repo-specific configurations You can now delete individual configurations for any repository directly from the dashboard. This makes it easier to reset a repo’s settings and have its PRs reviewed using the team’s global configuration instead. ⚙️ Review Cadence control Some teams reported too many comments being triggered when multiple…
-
Best SAST Tools for Code Security
Spotting security vulnerabilities in your code as early as possible is crucial, and Static Application Security Testing (SAST) plays a big role in that. Choosing between all the tools out there can be overwhelming, but understanding what makes the best SAST tools stand out will help you protect your applications more efficiently. This guide will…
-
Top 5 Newsletters for Engineering Leaders
At Kodus, we face the daily challenge of helping teams maintain code quality, scale engineering, and simplify the code review process. And part of our job is to stay connected with good references: content that helps engineering leaders make better decisions, fine-tune processes, and strengthen team culture. That’s why we’ve put together a few newsletters…
-
1.0.31 – Smarter rules and Kody on any repository
Improvements & New Features 📦 Kody Rules with full PR scope Kody Rules can now run with full pull request context, instead of analyzing files in isolation. With this update, rules can access the PR title, description, file list, and complete diffs — making it possible to write more powerful and contextual validations. Examples of…
-
Best Practices for Code Review in JavaScript
JavaScript gives you freedom, but with freedom comes risk. Without a well-defined code review process in JavaScript, it’s easy to let subtle bugs, inconsistent patterns, and even security vulnerabilities slip into your codebase. If you’re part of a team maintaining a JavaScript project—whether front-end, back-end with Node.js, or fullstack—code review needs to be a core…
-
1.0.30 – Kody Issues, more flexible settings, less noise
Improvements and New Features ✨ Kody Issues: automatically track unimplemented suggestions You can now automatically track and manage Kody suggestions that weren’t implemented in closed PRs. Kody Issues works like sonar—giving you a clear view of pending improvements and ensuring critical feedback isn’t forgotten. Automatic tracking: captures suggestions not applied when the PR is closed…
-
How to minimize the number of suggestions in PRs that change third-party files
When someone edits files inside third-party folders, like vendor, generated, or some internal lib, it’s common for Kody to start generating suggestions on those parts. The problem is that, in most cases, the team doesn’t even plan to review those points, since they’re areas of the code that usually aren’t changed manually. If the goal…
-
Best Practices for Python Code Review + Checklist
Doing code review in Python goes way beyond just looking for obvious bugs. It’s one of the most important steps to make sure the code going to production is clean, safe, and easy to maintain. In a team working with a dynamic language like Python, where the compiler won’t catch everything for you, code review…
-
How to adapt Kody for teams that open lots of small PRs
When the team works with lots of small PRs, it’s normal for people to start complaining that even when changing a comment, Kody is bringing suggestions. This happens because, by default, she analyzes any open PR, regardless of its size or type of change. If the goal is to keep reviews lighter and focused only…