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 PRs are described

Let’s see how to enable, customize, and make the most of this feature.

Enable automatic summary generation

If your team opens PRs without descriptions or with generic text like “fix” or “update,” this is the setting that will save you. To enable it:

1. Go to Settings → PR Summary
2. Turn on the Enable Automatic Summary Generation option

From that point on, every PR will automatically have a summary written by Kody. This ensures there is always an initial description, even if you later adjust it manually. 💡 Tip: If your team already writes good descriptions but wants to complement them with additional context, skip to the behavior modes section.

Choose how Kody handles existing descriptions

Not every PR starts from scratch. Sometimes the author already writes a description, but you want Kody to complement or reorganize it. That is where the behavior modes come in: 🔸 Replace (default) → Discards the original description and creates one from scratch. Ideal if the team has no standard or wants to completely unify the style. 🔸 Concatenate → Keeps what was already there and adds Kody’s summary at the end. Good for when the author provides human context (for example, the reason for the change) and you want to add a technical summary. 🔸 Complement → Merges the two texts, keeping what already makes sense and adding only new or relevant information. Great for enriching well-written descriptions without making them repetitive. 💡 Practical tip: If your team already writes detailed PRs but wants to ensure nothing important is left out, use Complement.

Customize the focus with instructions

Kody is good at writing summaries, but she gets even better when you tell her exactly what you want. In the Custom Instructions field, you can guide the focus of the analysis. Some examples:

• “Focus on changes affecting performance and security.”
• “List modified public APIs and database schema changes.”
• “Highlight changes impacting the checkout flow.”

The clearer you are, the more useful the result will be. 💡 Pro tip: If your team works in different areas (for example, backend, frontend, data), it is a good idea to create different instructions for each repository.

Review with the PR Summary Preview

Before the summary is sent to your Git tool, you can view the Preview directly in Kodus. To do this:

• Go to the PRs tab in Kodus
• Click the desired PR
• See the generated summary before publishing

This is useful for:

• Adjusting tone and focus before everyone reads it
• Fixing any possible misinterpretations
• Ensuring critical information is included

What this changes in daily work

With PR Summary configured, your team will spend less time trying to understand PRs and more time reviewing what truly matters.