skills.rest
rwc9u
rwc9uCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

team-pr-stats

Track merged pull request counts per developer across a GitHub organization.

Updated Feb 4, 2026
Search Tags:#github#pull-requests#gh-cli#ruby-script#team-stats#pr-metrics
One-click install
npx skills add https://github.com/rwc9u/claude-config --skill team-pr-stats
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-pr-stats
Source: https://github.com/rwc9u/claude-config/tree/main/skills/team-pr-stats
Command: npx skills add https://github.com/rwc9u/claude-config --skill team-pr-stats

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ruby, gh, and includes scripts (resource) components.

What problem does it solve?

Aggregate and present merged pull request counts per developer across a GitHub organization to remove manual searching and spreadsheet assembly and make team output easy to review.

Core Features & Use Cases

  • Monthly breakdowns by developer: Counts merged PRs for each team member across a configurable number of past months.
  • Org-wide or per-repo scope: Run across all organization repositories or limit to a single repository.
  • CSV or markdown output for reporting: Export results for spreadsheets or present immediately as a markdown table; highlights top contributors and month-over-month trends.
  • Use Case: Engineering leads and managers can compare team activity over time, identify trends, and export data for retrospectives or reporting.

Quick Start

Run the included Ruby script with the organization and team parameters to generate a markdown table or CSV of merged PR counts by developer.

Frequently Asked Questions about team-pr-stats

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

FAQPage Schema
How do I track merged pull request counts per developer across a GitHub organization?▼

To track merged pull request counts per developer, run the provided Ruby script with gh CLI authentication to aggregate PR data by month across all organization repositories or a single repo. It produces markdown or CSV output comparing team output trends.

Can I export GitHub pull request metrics to a CSV or markdown table for reporting?▼

Yes, you can export GitHub pull request metrics to CSV or markdown. The script outputs aggregated merged PR counts per developer, highlighting top contributors and month-over-month trends for immediate presentation or spreadsheet analysis.

Do I need Ruby and gh CLI installed to aggregate GitHub team stats?▼

Yes, you need both Ruby and the gh CLI installed to aggregate GitHub team stats. The script requires gh CLI authentication for network access to query repositories and a Ruby runtime to execute the aggregation logic.

What is the best way to visualize merged PRs by developer for engineering retrospectives?▼

The best way to visualize merged PRs by developer is running the script to generate a markdown table showing monthly breakdowns. It scopes queries across your organization to compare team activity and identify output trends for retrospectives.

How do I limit pull request metrics tracking to a specific repository instead of the whole GitHub organization?▼

To limit pull request metrics tracking to a specific repository, specify the target repository when running the script. It scopes the merged PR count queries to that single repo instead of aggregating across all organization repositories.

Related Skills

Explore More Software Engineering Skills→
steven508508steven508508
1

github

Automate GitHub pull request status checks and workflow runs via gh CLI.

Community
Intermediate
nhattran998nhattran998

retro

Analyze commit history and code quality metrics into weekly team retrospectives.

Community
Intermediate
LdotJdotLdotJdot
45

github

Automate GitHub repository management and PR/issue workflows via gh CLI.

Community
Intermediate
shogo-labsshogo-labs
12

dev-activity-track

Aggregate GitHub commits, PRs, and reviews into per-developer dashboards.

Official
Advanced