Top-level metrics
The top metrics focus on:- Comments posted: how much review activity cubic generated.
- Issues fixed after comment: how often developers acted on findings.
- Average time to merge: merge speed compared against a pre-cubic baseline.
The average time to merge metric requires at least 10 merged PRs in the selected period. Below
that threshold, a message prompts you to merge more PRs before the metric becomes available.
Critical issues
The critical issues section highlights high-impact findings across recent PRs. Use it for quick triage and recurring-pattern detection.Your team in numbers
The sidebar summarizes team-level usage and quality:- PRs reviewed
- Downvote rate (lower is better)
- CLI sessions
- Fix PRs merged
Downvotes also help cubic learn. When you downvote a suggestion, cubic remembers that feedback and
adjusts future reviews accordingly. See Memory and learning for
details.
Custom agents
The custom agents table shows which agents flag the most issues and how many of those issues were fixed.Tips for interpreting these metrics
- Prioritize fixed issues over raw comment volume.
- Use downvote rate as a quality signal for prompt/rule tuning.
- Compare trends over 30+ days instead of one short window.
- Treat merge-time change as directional, not absolute truth.