Generate condensed team contributor statistics report comparing two years
Generate a comprehensive team contributor report comparing two years with PR/commit metrics, insights for every team member, and an interactive dashboard with charts.
/plugin marketplace add rryter/claude-plugins/plugin install consulting@twy-marketplaceYou are tasked with generating a concise, actionable team contributor statistics report.
Run the script to find the top 10 contributors by PR count for the current year:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/find-top-contributors.sh 2025 10
Parse the output which will be in format: github_username:pr_count
Store the list of GitHub usernames.
For each GitHub username from Step 1, you need to identify ALL possible git identities (email addresses, name variations, employee IDs) they might have used in commits.
For each contributor:
First, get their name from a sample PR:
gh pr list --state all --author "USERNAME" --limit 1 --json author
Then search for all possible identities in git history using variations of:
Use commands like:
git log --all --format="%an <%ae>" | grep -iE "(name_pattern|email_pattern)" | sort -u
Create a temporary file /tmp/contributor-identities.txt with one line per contributor in format:
github_user|name_pattern|email_pattern|employee_id_pattern
Example:
rryter|reto|ryter|reto.ryter@css.ch|reto@twy.gmbh
rfe-css|raphael|felber|p17875|raphael.felber@css.ch
IMPORTANT: Be thorough in finding all identities. Check:
Run the PR metrics script with the GitHub usernames (comma-separated):
bash ${CLAUDE_PLUGIN_ROOT}/scripts/gather-contributor-metrics.sh "user1,user2,user3" 2024 2025
This will output JSON with PR counts and monthly breakdowns for both years (2024 and 2025). Save the output location.
Run the git metrics script with the identities file:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/gather-git-metrics.sh /tmp/contributor-identities.txt 2024 2025
This will output JSON with commit counts and monthly breakdowns for both years (2024 and 2025).
Important: Git metrics exclude merge commits (using --no-merges flag) to focus on actual code contributions rather than integration work. Save the output location.
Read both JSON outputs and merge the data by matching contributors. You should now have for each contributor:
Generate a concise, actionable report and save it to /tmp/team-stats-report.md following this structure:
Single comprehensive table combining all metrics: | Developer | 2024 Commits | 2024 PRs | 2025 Commits | 2025 PRs | Commit Δ | PR Δ | Commits/PR 2024 | Commits/PR 2025 | Trend |
Include trend indicators: 🚀 (explosive growth), 📈 (growth), 📉 (decline), ⚠️ (concern), ✅ (stable)
IMPORTANT: Provide insights for ALL contributors found in the data (typically 10+ people). Do not skip anyone.
For each contributor, provide 2-4 concise bullet points:
Format per contributor:
**name (role/id):** Status emoji
- Key insight 1
- Key insight 2
- Key insight 3 (if notable)
- Concern/highlight (if applicable)
Sort contributors by their total impact (commits + PRs) in descending order.
Bullet-point format only:
High Priority (Next 30 days):
Medium Priority (Next 90 days):
Strategic Concerns:
Keep current structure but use concise bullets:
Single paragraph covering:
Generate a comprehensive, scannable report in Markdown with:
IMPORTANT: Do not summarize or skip contributors. The report should be comprehensive enough to understand every team member's contribution and status.
Save the report to /tmp/team-stats-report.md using the Write tool.
Generate the final interactive HTML dashboard that includes the report and charts:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/generate-interactive-charts.sh /tmp/contributor-metrics-*.json /tmp/git-metrics-*.json /tmp/team-stats-graphs /tmp/team-stats-report.md
This will create an interactive HTML file at /tmp/team-stats-graphs/team-stats-charts.html with:
After generating the dashboard, inform the user they can open the HTML file in their browser.
# Step 1: Find top contributors
bash ${CLAUDE_PLUGIN_ROOT}/scripts/find-top-contributors.sh 2025 10
# Step 2: You'll search for identities manually using git log and grep
# Step 3: Gather PR metrics
bash ${CLAUDE_PLUGIN_ROOT}/scripts/gather-contributor-metrics.sh "rryter,rfe-css,tthttl,zemph,vorderpneu" 2024 2025
# Step 4: Gather git metrics (after creating identities file)
bash ${CLAUDE_PLUGIN_ROOT}/scripts/gather-git-metrics.sh /tmp/contributor-identities.txt 2024 2025
# Step 5: Analyze and merge data
# Step 6: Generate report (save to /tmp/team-stats-report.md)
# Step 7: Generate interactive dashboard with embedded report
bash ${CLAUDE_PLUGIN_ROOT}/scripts/generate-interactive-charts.sh /tmp/contributor-metrics-*.json /tmp/git-metrics-*.json /tmp/team-stats-graphs /tmp/team-stats-report.md
Begin the analysis now. Start with Step 1.