gh-contribution-report

Generate structured Markdown contribution reports from GitHub commits and pull requests.

Updated Jan 10, 2026
One-click install
npx skills add https://github.com/RDCrystalLab/agentic-plugins --skill gh-contribution-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-contribution-report
Source: https://github.com/RDCrystalLab/agentic-plugins/tree/main/plugins/vault-assistant/skills/gh-contribution-report
Command: npx skills add https://github.com/RDCrystalLab/agentic-plugins --skill gh-contribution-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual effort of collecting GitHub commits and pull requests across organizations and turning scattered activity data into structured contribution reports.

Core Features & Use Cases

  • GitHub Activity Collection: Fetch commits and pull requests from multiple organizations using GitHub CLI with pagination-aware workflows.
  • Obsidian Report Generation: Create monthly and annual Markdown reports with statistics, activity analysis, and navigable report structures.
  • Use Case: Generate a yearly engineering contribution summary from multiple GitHub organizations, including repository activity, PR history, and project highlights.

Quick Start

Ask the gh-contribution-report skill to generate a monthly and annual GitHub contribution report for the specified organizations and year.

Frequently Asked Questions about gh-contribution-report

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

FAQPage Schema
How do I generate a GitHub contribution report for multiple organizations?

To generate a GitHub contribution report for multiple organizations, the Skill fetches commits and pull requests via GitHub CLI, parses the activity data, and produces structured Markdown reports with aggregated statistics.

Can I create developer performance summaries and track engineering activity in Obsidian?

You can track engineering activity in Obsidian by generating monthly and annual Markdown reports that include repository activity, PR history, and project highlights formatted for navigable Obsidian-based reporting workflows.

Do I need GitHub CLI to collect commit and pull request data?

You need GitHub CLI to collect commit and pull request data because the Skill relies on its pagination-aware workflows to fetch activity across multiple organizations before parsing and validating the aggregated statistics.

What is the best way to summarize yearly commits and pull requests across GitHub organizations?

The best way to summarize yearly commits and pull requests across GitHub organizations is to automate data collection and Markdown report generation, which removes manual effort and validates aggregated contribution statistics.

What are the limitations of automating GitHub contribution tracking with Markdown reports?

Limitations of automating GitHub contribution tracking include relying entirely on GitHub CLI data availability and requiring accurate commit and PR parsing to validate aggregated statistics without manual data correction.