kpi-pr-throughput

Measure PR merge throughput metrics across agent sessions with quality gates.

1|Updated Dec 15, 2025
One-click install
npx skills add https://github.com/Anveio/conveaux --skill kpi-pr-throughput
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kpi-pr-throughput
Source: https://github.com/Anveio/conveaux/tree/main/.claude/skills/kpi-pr-throughput
Command: npx skills add https://github.com/Anveio/conveaux --skill kpi-pr-throughput

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This KPI helps teams measure and optimize PR throughput while maintaining quality.

Core Features & Use Cases

  • Primary Metric: PRs merged per session
  • Supporting Metrics: Time to Merge, Review Cycles, First-Pass Approval Rate, Revert Rate
  • Measurement: During a session, track PR merges using GitHub CLI and JSON outputs. For example:
  • Use Case: A team wants to maximize the number of quality PRs merged per agent session without increasing defect risk.

Quick Start

Count merged PRs by this agent: gh pr list --state merged --author @me --json number | jq length

Frequently Asked Questions about kpi-pr-throughput

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I measure PR throughput in my Git workflow?

PR throughput measures the rate of quality pull requests merged per session. Track it using GitHub CLI to count merged PRs by author, then aggregate metrics like time to merge, review cycles, and first-pass approval rate across sessions to optimize your team's merge velocity.

Can I track PR metrics while maintaining quality gates?

Yes. This approach integrates quality gates with GitHub CLI and verification scripts to ensure merges occur only on green builds. You measure throughput—PRs merged per session, time to merge, revert rate—while enforcing automated checks that prevent low-quality merges.

What metrics should I monitor to optimize PR workflows?

Monitor PRs merged per session, time to merge, review cycles, first-pass approval rate, and revert rate. These supporting metrics reveal bottlenecks in your PR process and help identify whether delays stem from review cycles, build failures, or approval friction.

How do I track PR metrics across multiple sessions?

Use GitHub CLI to extract merged PR data as JSON output, then aggregate results across sessions. Session-scoped aggregation lets you compare throughput trends over time and identify which sessions or workflows achieve the highest quality-adjusted merge rates.

Does this approach work with automated agent PR workflows?

Yes. This KPI is designed for automated agent PR workflows in software repositories. It measures agent-generated PR throughput using GitHub CLI and verification scripts, ensuring metrics reflect bot activity separately from human contributors.

What's the best way to prevent quality loss while increasing PR throughput?

Balance throughput optimization with quality gates—automated checks that block merges on failed builds. Monitor revert rate and first-pass approval rate alongside merge speed. If reverts spike, throughput gains indicate quality compromise and require workflow adjustment.