PRs Reviewed
Architect & Collaboration Metrics
Counts the number of pull requests you reviewed within your team.
💡 Like peer-grading in a class, reviewing teammates' code improves both the code quality and your own understanding of the codebase.
What It Measures
Counts the number of pull requests you reviewed within your team.
Why It Matters
Monitoring engagement in the code review process
Tracking your contribution to team quality
How It's Calculated
Counts each review action where you and the author are on the same team.
COUNT(review_actions WHERE reviewer_team = author_team)Concrete Example
If you reviewed 15 pull requests from your team this week, you're actively contributing to code quality, that's 3 reviews per day on a 5-day week.
What Does a Healthy Score Look Like?
Higher is generally better, active reviewing supports team quality.
Healthy
5+ team PRs reviewed per week
Watch Out
2–4 team PRs reviewed per week
Needs Attention
0–1 team PRs reviewed, not participating in code review
What Moves This Metric?
Goes up when…
More pull requests opened by teammates giving more to review
Active participation in code review culture
Review rotation assignments directing more PRs to you
Goes down when…
Heavy individual workload leaving less time for reviewing
Review responsibilities concentrated on fewer team members
Low overall PR activity reducing available reviews
Start Tracking PRs Reviewed
Connect GitHub and Shortcut in minutes. All metrics update automatically.
Engineering metrics and developer well-being platform. Track 50+ metrics, AI-powered insights, and Dynamic Archetypes for just $10/active user/month.
contact@projcity.com