Korbit Insights

Korbit Insights

Korbit Insights is your engineering team’s automated reporting dashboard. It helps engineering managers, tech leads, and execs get a clear view into team performance, code quality, release activity, and potential risks—without the need to manually compile metrics or spreadsheets. Insights are automatically generated from your team’s PR activity across GitHub, GitLab, and Bitbucket.

Developer Insights

The Developer Insights report gives a clear, story-driven look at what a developer has worked on over a specific time period. It includes helpful metrics like total merged pull requests, average PR duration, and how often review feedback was addressed, giving teams a simple way to understand pace and engagement.

But it's not just about numbers. The report also highlights each developer's focus areas like refactoring, bug fixes, or new features—and gives a plain-language summary of their most impactful work. To make it a bit more fun, each developer gets a codename based on the kind of work they've done.

It's useful for things like:

  • 1:1 check-ins
  • Sprint recaps or retros
  • Sharing individual highlights with stakeholders
  • Recognizing team members in a more personal way

By blending activity data with human-readable summaries, this report helps teams reflect, spot trends, and appreciate the work being done.

Team Insights

The Team Insights report gives a clear, big-picture view of what a development team has accomplished over a set period of time. It pulls together key stats like merged pull requests and average PR duration, while also highlighting the areas the team focused on like new features, bug fixes, or UX improvements.

More than just metrics, the report tells the story behind the work. It captures meaningful contributions, whether that’s improving APIs, refining onboarding, or polishing the user experience. Each team gets a lighthearted codename that reflects their impact and adds a bit of fun to the report.

Teams often use this for:

  • Sprint or milestone retros
  • Sharing progress with stakeholders
  • Engineering all-hands or demos
  • Recognizing team contributions

The report also surfaces how the team collaborated like cross-repo coordination or shared efforts on complex features. It’s a helpful way to reflect on what’s been shipped, how the team worked together, and where their efforts made the biggest difference.

Release Notes

The Release Summary report gives a straightforward overview of what’s been shipped during a specific timeframe. It highlights key changes across new features, improvements, bug fixes, deprecations, and security updates, making it easy to see what’s new and why it matters.

The report is organized into clear sections so that anyone can quickly scan and understand the latest product updates, regardless of their technical background. It’s a simple way to keep everyone on the same page, from stakeholders to support teams.

Common ways teams use it:

  • Sharing updates with leadership or external stakeholders
  • Keeping support and success teams in the loop
  • Powering changelogs or in-app “What’s New” updates
  • Supporting retrospectives or internal reviews

It’s an easy way to track progress, reflect on what’s been delivered, and make sure no one misses the important stuff.

Saving Reports

After you generate a report, you can save the query to your account. This allows you to run the same report easily in the future.

Actions

Once you have generated a report, you can listen to the report, copy as text or download as a PDF.

issue screenshot


MIT 2025 © Nextra.