github-pr-stats

Name: github-pr-stats
Author: tomevault-io

Data Community

Repo stars 0
Author updated Live
Author repo skills-registry

Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network

Domain: Data
Compatible agents: Claude Code
Cursor
Cline
Codex
Windsurf
Gemini CLI

+20
Trust score: 88 / 100 · community maintained
Author / version / license: @tomevault-io · no license declared
Token usage: Lean
Setup complexity: Plug-and-play
External API key: Not required
Operating systems: Unspecified (assume cross-platform)
Runtime requirements: Python
Permissions: Read-only
Write / modify
Network behavior: Local-only
Install commands: 26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview github-pr-stats.preview

---
name: github-pr-stats
description: Compute PR statistics (total, merged, closed, avg merge time, top contributor) from GitHub API d…
category: data
runtime: Python
---

# github-pr-stats output preview

## PART A: Task fit
- Use case: Compute PR statistics (total, merged, closed, avg merge time, top contributor) from GitHub API data using Python or jq. Use when this capability is needed. After fetching PR data from the GitHub API, use Python or jq to compute: runs entirely locally; runs on Python. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Overview / Fetching PRs for a Date Range / Python: Compute Stats from JSON” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Compute PR statistics (total, merged, closed, avg merge time, top contributor) from GitHub API data using Python or jq. Use when this capability is needed. After fetching PR data from the GitHub API, use Python or jq to compute: runs entirely locally; runs on Python. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Overview / Fetching PRs for a Date Range / Python: Compute Stats from JSON” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.

SKILL.md SKILL.md

---
name: github-pr-stats
description: Compute PR statistics (total, merged, closed, avg merge time, top contributor) from GitHub API d…
category: data
source: tomevault-io/skills-registry
---

# github-pr-stats

## When to use
- Compute PR statistics (total, merged, closed, avg merge time, top contributor) from GitHub API data using Python or jq…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.

## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.

## Execution rules
- Organize steps around “Overview / Fetching PRs for a Date Range / Python: Compute Stats from JSON” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.

## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.

Evidence boundary and execution chain

The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.

skill "github-pr-stats" {
  input      -> user goal + target files + boundaries + acceptance criteria
  context    -> Overview / Fetching PRs for a Date Range / Python: Compute Stats from JSON
  rules      -> SKILL.md triggers / order / output contract
  runtime    -> Python | read files, write/modify files | mostly runs locally
  guardrails -> usually needs no extra API key + small-sample validation + diff/log review
  output     -> copyable result + checklist + next iteration
}

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Compute PR statistics (total, merged, closed, avg merge time, top contributor) from GitHub API data using Python or jq. Use when…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Overview”, “Fetching PRs for a Date Range”, “Python: Compute Stats from JSON”, “Notes on State Values”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name github-pr-stats directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Overview / Fetching PRs for a Date Range / Python: Compute Stats from JSON” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

GitHub PR Statistics

Overview

After fetching PR data from the GitHub API, use Python or jq to compute:

Total PR count
Merged vs closed counts
Average time-to-merge (days)
Top contributor by PR count

Fetching PRs for a Date Range

# Using gh search (handles pagination, date filtering)
gh pr list -R cli/cli \
  --search "created:2024-12-01..2024-12-31" \
  --state all \
  --limit 500 \
  --json number,author,createdAt,mergedAt,closedAt,state

Python: Compute Stats from JSON

import json
from datetime import datetime, timezone
from collections import Counter

# Load PR data (from gh pr list --json output)
with open('prs.json') as f:
    prs = json.load(f)

total = len(prs)

# Count merged vs closed-but-not-merged
merged = [pr for pr in prs if pr['mergedAt']]
closed = [pr for pr in prs if not pr['mergedAt'] and pr['state'] == 'CLOSED']

# Average time to merge (creation -> mergedAt), in days
def parse_dt(s):
    return datetime.fromisoformat(s.replace('Z', '+00:00'))

merge_days = []
for pr in merged:
    created = parse_dt(pr['createdAt'])
    merged_at = parse_dt(pr['mergedAt'])
    delta = (merged_at - created).total_seconds() / 86400
    merge_days.append(delta)

avg_merge_days = round(sum(merge_days) / len(merge_days), 1) if merge_days else 0.0

# Top contributor
authors = Counter(pr['author']['login'] for pr in prs)
top_contributor = authors.most_common(1)[0][0]

print(json.dumps({
    "total": total,
    "merged": len(merged),
    "closed": len(closed),
    "avg_merge_days": avg_merge_days,
    "top_contributor": top_contributor
}, indent=2))

Notes on State Values

gh pr list --json returns state as "OPEN", "CLOSED", or "MERGED"
mergedAt is non-null only for merged PRs
A PR with state == "CLOSED" and mergedAt == null is truly closed (not merged)

Notes on the Search API

created:2024-12-01..2024-12-31 is inclusive on both ends
Dec 31 means up to 2024-12-31T23:59:59Z
Use --limit 500 to avoid truncation for active repos

Source: cxcscmu/SkillLearnBench — distributed by TomeVault.

Install command

One-click installPick a runner, click Copy, paste into your terminal, press enter

npx skills add tomevault-io/skills-registry/cxcscmu--skilllearnbench--github-pr-stats -y

Open general install guide

View skill source

Works with

Claude Code
Cursor
Cline
Codex
Windsurf
Gemini
OpenCode
Roo Code
AAide
+Augment
GitHub Copilot
OpenClaw
KKiro
Junie
WWarp
Goose
Trae
Kilo Code
OpenHands
Amp
Zencoder
CContinue
AIAider
CodeBuddy
CodeGeeX
Replit Agent

Security audit

88 / 100

Community

未声明 license/许可。
未声明 version。
未限定 allowed-tools，默认拥有全部工具权限。

Metadata

Source: github
tomevault-io/skills-registry
中文

More by @tomevault-io

Category & tags

Category Data