Day: August 11, 2025
-
How to use the Cockpit
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…
-
How to Use Kody Issues
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…
-
How to Use the PR Summary
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…
-
How to Configure and Improve Kody’s Suggestions
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…
-
Setting Up Kody Rules for Code Reviews
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,…
-
Java Code Review – Best Practices + Checklist
Let’s be honest: a great java code review is the single biggest unlock for a high-performing engineering team. It’s more than a process, more than a box to tick before merging. It’s the moment where code transforms from a solo effort into a shared asset. It’s where quality is forged, knowledge is spread, and disaster…