Skip to main content
The Delivery and effectiveness tab focuses on how quickly PRs move from creation to merge and where bottlenecks appear.

Velocity metrics

The top velocity metrics are:
  • Median wait-to-first-review: how long PRs wait for first human review.
  • Average review cycles until merge: how many revision rounds PRs go through.
  • Average PR cycle time: total creation-to-merge time.
  • Average time in review: first review to final approval.
  • Average time from approval to merge: post-approval operational delay.
A decreasing trend is positive — it means PRs are getting reviewed faster. The trend indicator reflects this: a downward change appears in green.

Throughput metrics

  • PRs merged per developer: average merged output for active authors.
  • PRs reviewed per developer: average review load for active reviewers.

Code volume

Track lines added and lines deleted as activity context, not as a quality score.
Lines of code are a measure of activity, not productivity. A large refactor that deletes more lines than it adds can be more valuable than a feature with thousands of new lines. Use code volume as context alongside the other metrics, not as a standalone indicator.

Team members table

The team members table includes per-developer delivery and review metrics:
ColumnDefinition
PRs reviewed by cubicMerged PRs by this author that received a cubic AI review.
Total cubic commentsNumber of review comments cubic posted on this author’s PRs.
Comments addressedNumber of cubic comments the author subsequently fixed.
Reviews givenNumber of PR reviews this developer submitted on other people’s PRs.
Avg review cyclesAverage number of review cycles for this author’s merged PRs.
Lines addedTotal lines of code added by this author.
Lines deletedTotal lines of code deleted by this author.
Click column headers to sort. Use the search field to filter by GitHub username.

CSV export

Click the download button above the table to export the current view as a CSV file. The export respects your active filters and time period selection. The filename includes the export date for easy tracking. Use this export for lightweight reporting or trend tracking outside cubic.

Tips for interpreting delivery metrics

  • Compare trends, not absolutes.
  • Read metrics together to find bottlenecks.
  • Large PRs naturally increase cycle times and review rounds.