Skip to content
Skills Library
Data & analytics · Analysis

github-contribution-period-analysis

/github-contribution-period-analysis

Analyze one GitHub user's code contribution activity in a specified UTC time window and generate a Markdown report focused on practical contributions (authored merged PRs, PRs merged by the target user, and authored commits) across accessible public and private repositories. Use when users ask to evaluate real engineering contribution over a period and want evidence links.

Licence
MIT
Last repository change
20.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
6
Scripts
1
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 20.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 1 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/github_contribution_report.py

What it does and when to use it

Analyze one GitHub user's code contribution activity in a specified UTC time window and generate a Markdown report focused on practical contributions (authored merged PRs, PRs merged by the target user, and authored commits) across accessible public and private repositories. Use when users ask to evaluate real engineering contribution over a period and want evidence links.

Original author description

Analyze one GitHub user's code contribution activity in a specified UTC time window and generate a Markdown report focused on practical contributions (authored merged PRs, PRs merged by the target user, and authored commits) across accessible public and private repositories. Use when users ask to evaluate real engineering contribution over a period and want evidence links.

How it works

  1. Core Goal
  2. Workflow
  3. Command
  4. Output Semantics
  5. Important Constraints
  6. References
  7. Scripts
Original SKILL.md headings · 54 lines, 250 words
SKILL.md preview
---
name: github-contribution-period-analysis
description: Analyze one GitHub user's code contribution activity in a specified UTC time window and generate a Markdown report focused on practical contributions (authored merged PRs, PRs merged by the target user, and authored commits) across accessible public and private repositories. Use when users ask to evaluate real engineering contribution over a period and want evidence links.
---

# GitHub Contribution Period Analysis

## Core Goal
- Build an evidence-based Markdown report for one target GitHub user in a UTC time window.
- Focus on practical code contribution signals: merged PR and commit activity.
- Cover both own repositories and other repositories, limited by credential access.

## Workflow
1. Prepare authentication for GitHub API access.
2. Run `scripts/github_contribution_report.py` with target user and time window.
3. Review the generated Markdown report and inspect evidence links.

## Command

```bash
python3 scripts/github_contribution_report.py \
  --user <github-login> \
  --start 2026-03-01 \
  --end 2026-03-08 \
  --output /tmp/github-contribution-report.md
```

## Output Semantics
- Included contribution types:
  - Authored merged PRs.
  - PRs merged by the target user (maintainer merge work).
  - Authored commits.
- Excluded activity types:
  - Comments, reviews, stars, watches, forks.
- The report contains:
  - Scope and coverage notes.
  - Summary metrics.
  - Substantive work categories inferred from PR/commit evidence.
  - Work content highlights with representative evidence links.
  - Repository breakdown.
  - Per-repository concrete change details (for every changed repository).
  - Contribution timeline.
  - Top contribution tables.
  - Evidence appendix with PR/commit URLs.

## Important Constraints
- SSH key alone is for `git` transport and does not directly authorize GitHub REST API calls.
- Private repository coverage needs authenticated API access, typically via `GITHUB_TOKEN`/`GH_TOKEN` or `gh auth token`.
- GitHub Search API has a 1000-item cap per query. For very active users, split the time range and run multiple reports.

## References
- `references/env.md`
- `references/data-model.md`
- `references/markdown-template.md`

## Scripts
- `scripts/github_contribution_report.py`
Files in this package (6)
  • SKILL.md 2 KB
  • agents/openai.yaml 1 KB
  • references/data-model.md 2 KB
  • references/env.md 1 KB
  • references/markdown-template.md 1 KB
  • scripts/github_contribution_report.py 49 KB

Versions

The database has no other skills named github-contribution-period-analysis.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 0b129f82c354 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100pr-leaderboard
    Use when asked to analyze, rank, or explore merged PRs in a GitHub repo — "who merged what this week", "PR leaderboard", "rank contributors", "top authors", "PRs merged since X", weekly/monthly merge activity — for the current repo or any owner/repo.
  • 90github-activity-analyzer
    Comprehensive GitHub contribution analysis for any time period. Use when user asks about recent work, wants to review their contributions, needs a status update, or requests activity summary. Supports flexible formats: relative time (days/weeks/months/years), full years (2025),…
  • 87analyze-contribution-generate-viz
    Template for visualizing analyze-contribution's calculations. ONLY use this skill when explicitly asked to do so.
  • 100pr-trends
    Generate weekly and monthly pull request trend tables for a git repository, including created PRs, merged PRs, average days to merge, and lines changed. Use when a user asks for PR throughput trends, repo contribution trends, weekly or monthly PR summaries, merge velocity, or a…
  • 90developer-activity-story
    Analyze a GitHub user or developer's visible activity across pull requests, issues, commits, reviews, repositories, and discussions. Use when asked to summarize a developer, create a contributor profile, generate a weekly or monthly GitHub roundup, analyze work patterns, prepare…
  • 100ingest-github
    Use when the user says /ingest-github <owner/repo> [--days N], or asks to ingest, capture, sync, pull, mirror, or import a GitHub repo's recent activity (merged PRs, issues, commits) into the vault, second brain, or knowledge graph, or wants repo history queryable by graphify or…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.