Category: Kody Tips and Guides

The Cockpit is the central dashboard for tracking productivity and code health. It brings together development metrics, quality indicators, and the impact of Kody’s suggestions, all in one place. How you can use it: Start with the overview Right away, you see a summary of the most important metrics to track your team’s health: Deploy…

When a PR is closed, it is common for some suggestions to be left for later — whether because they were not a priority at that moment or because the team decided to focus on the main delivery. The problem is that “later” often turns into “never”. Kody Issues solves this by automatically creating a…

Everyone has opened a Pull Request and thought: “What actually changed here?” Kody’s PR Summary solves exactly that. It writes a clear and objective summary of the changes without you having to spend time describing them line by line. When properly configured, it helps your team: Get context faster Reduce back-and-forth during reviews Standardize how…

When Kody starts reviewing your PRs, she brings a full package of suggestions, ranging from simple adjustments to critical issues. This ensures coverage, but without configuration, the review can become cluttered and lose focus. The secret is to adjust Kody so she talks less, but with more impact. Here’s how. Adjust the limit and severity…

The Kody Rules are like internal laws for your repository. They allow Kody to automatically enforce coding standards, security, and best practices during code review. These rules can range from naming conventions, such as React components must be in PascalCase, to critical business requirements, such as payment operations must be idempotent. By creating clear rules,…

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…

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…

When a team has never had a clear review process, it’s common for PRs to get merged after just a quick read — with no standard, no technical criteria, and no visibility into what really matters. The idea here is to start light but with real impact. If you’re using Kody as the starting point…

When the team is on a tight deadline, the focus shifts to delivering — fast. But that doesn’t mean quality has to be pushed aside. The key here isn’t to stop reviewing, but to adjust Kody to only act where it really matters. With the right settings, you can keep the review process running, but…