GitHub Shipment Tracker

VerifiedSafe

Analyzes merged pull requests and closed issues across GitHub repositories to generate an interactive HTML report summarizing what was shipped over a given time period. Useful for visualizing team progress, sprint results, or quarterly deliveries.

Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude CodeCursorWindsurfCopilotCodex
#github-report#shipment-tracking#pr-analysis#timeline-visualization

Recommended for

Automated summary

Generates an interactive HTML report of shipped items (merged PRs and closed issues) across GitHub repositories over a specified time period.

Strengths

  • Multi-repository analysis with a single command
  • Built-in interactive timeline visualization
  • Uses only Python standard library, no extra dependencies
  • Natural language time period parsing

Limitations

  • Requires the gh CLI tool to be installed and authenticated
  • Limited to 1000 results per API query
  • Does not capture non-PR/issue deliveries (e.g., direct deployments)
When to use it

When you need a visual overview of what was shipped over a given period for one or more GitHub repositories.

When not to use it

If you need a detailed analysis of individual commits or deployments, as the tool focuses on merged PRs and closed issues.

Security analysis

Safe
Quality score92/100

The skill uses gh CLI for read-only operations (list merged PRs and closed issues) and Python to generate a local HTML report. No destructive commands, no data exfiltration, and no obfuscation.

No concerns found

How this analysis is made

Examples

Single repository, last 30 days
Show me what was shipped in the past 30 days
Multiple repositories, last quarter
What did we ship last quarter across all our main repos?
Custom date range
Generate a shipment report for repo owner/repo from 2024-01-01 to 2024-03-31

name: shipment-tracker description: Generate a visual report of what was shipped in GitHub repositories over a specified time period by analyzing merged PRs and closed issues. license: MIT compatibility: Requires gh CLI tool and Python 3.8+ with no additional dependencies (uses only stdlib) metadata: author: GitHub Copilot version: "1.0" allowed-tools: gh python3 python

Shipment Tracker

Analyze one or more GitHub repositories to visualize what was shipped over a specified time period. Creates an interactive HTML report showing merged pull requests and closed issues with timeline visualization.

When to Use

  • User asks "what was shipped in the last X days/weeks/months"
  • User wants to see a report of completed work across repositories
  • User requests a "shipment report" or "delivery timeline"
  • User wants to visualize team progress over a quarter or sprint
  • User asks for examples: "show me what we shipped last quarter" or "what went out in the past 30 days"

Instructions

1. Parse Time Period

Accept natural language time periods from the user:

  • "past 30 days" / "last 30 days"
  • "last week" / "past week"
  • "last month" / "past month"
  • "last quarter" / "past 90 days"
  • "last 6 months"
  • "since YYYY-MM-DD"
  • "between YYYY-MM-DD and YYYY-MM-DD"

Convert to ISO 8601 date format for GitHub API queries.

2. Gather Repository Information

Ask the user which repositories to analyze:

  • Single repo: owner/repo
  • Multiple repos: owner/repo1 owner/repo2
  • If not specified, use current repository from git remote

3. Fetch Data with GitHub CLI

For each repository, fetch:

Merged Pull Requests:

gh pr list \
  --repo owner/repo \
  --state merged \
  --search "merged:>=YYYY-MM-DD" \
  --json number,title,author,mergedAt,url,labels \
  --limit 1000

Closed Issues:

gh issue list \
  --repo owner/repo \
  --state closed \
  --search "closed:>=YYYY-MM-DD" \
  --json number,title,author,closedAt,url,labels \
  --limit 1000

4. Generate HTML Report

Use the helper script scripts/generate-report.py to create an interactive HTML page:

python3 scripts/generate-report.py \
  --repos "owner/repo1,owner/repo2" \
  --since "2024-01-01" \
  --until "2024-03-31" \
  --output shipment-report.html

The script will:

  • Parse JSON data from gh CLI
  • Group items by repository and type (PR/Issue)
  • Create a timeline visualization
  • Generate statistics (total shipped, by author, by label)
  • Include filtering and sorting capabilities
  • Create a standalone HTML file with embedded CSS/JS

5. Open the Report

open shipment-report.html
# or on Linux:
xdg-open shipment-report.html

Output Format

The generated HTML report includes:

  1. Summary Section

    • Total PRs merged
    • Total issues closed
    • Date range analyzed
    • Repositories included
    • Top contributors
  2. Timeline Visualization

    • Interactive timeline showing when items were shipped
    • Color-coded by type (PR vs Issue)
    • Grouped by repository
  3. Detailed Lists

    • Filterable and sortable tables
    • Links to GitHub items
    • Author information
    • Labels and metadata
  4. Charts

    • Shipment velocity over time
    • Breakdown by repository
    • Contribution distribution

Examples

Example 1: Single Repository, Last 30 Days

User: "Show me what was shipped in the past 30 days"

Agent Actions:

  1. Determine current repo: gh repo view --json nameWithOwner
  2. Calculate date 30 days ago
  3. Fetch merged PRs: gh pr list --state merged --search "merged:>=2024-12-06" --json number,title,author,mergedAt,url,labels --limit 1000
  4. Fetch closed issues: gh issue list --state closed --search "closed:>=2024-12-06" --json number,title,author,closedAt,url,labels --limit 1000
  5. Generate report: python3 scripts/generate-report.py --repos "owner/repo" --since "2024-12-06" --output shipment-report.html
  6. Open report

Example 2: Multiple Repositories, Last Quarter

User: "Create a shipment report for github/copilot and github/copilot-cli for last quarter"

Agent Actions:

  1. Parse time: "last quarter" = past 90 days
  2. Calculate date: 90 days ago from today
  3. For each repo, fetch merged PRs and closed issues
  4. Generate combined report: python3 scripts/generate-report.py --repos "github/copilot,github/copilot-cli" --since "2024-10-07" --output shipment-report.html
  5. Open report

Example 3: Custom Date Range

User: "Show what we shipped between January 1st and March 31st 2024"

Agent Actions:

  1. Parse dates: since="2024-01-01", until="2024-03-31"
  2. Fetch data for date range
  3. Generate report: python3 scripts/generate-report.py --repos "owner/repo" --since "2024-01-01" --until "2024-03-31" --output shipment-report.html
  4. Open report

Notes

Date Parsing

  • Use ISO 8601 format (YYYY-MM-DD) for GitHub API queries
  • "Last quarter" = 90 days
  • "Last month" = 30 days
  • "Last week" = 7 days
  • Always calculate dates relative to current date

API Limits

  • GitHub CLI uses authenticated requests (higher rate limits)
  • Each query returns up to 1000 results
  • For very active repos, consider narrower time ranges
  • The skill will warn if hitting limits

Filtering Considerations

  • Only includes merged PRs (not closed without merging)
  • Only includes closed issues (not open)
  • Draft PRs are excluded
  • Private repositories require appropriate permissions

Performance

  • Fetching data for multiple repos is done in parallel when possible
  • Large datasets (hundreds of items) may take 10-30 seconds to process
  • Generated HTML is standalone and works offline after creation

Customization

Users can request:

  • Filtering by labels: "only show PRs with label:bug"
  • Filtering by author: "only show @username's contributions"
  • Grouping preferences: by week, by month, by repository
  • Chart types: timeline, bar chart, pie chart

Error Handling

If a repository is not accessible:

  • Skip it and continue with other repos
  • Show a warning in the report
  • Don't fail the entire operation

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/github-shipment-tracker-mmh8qr4q/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/github-shipment-tracker-mmh8qr4q' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/github-shipment-tracker-mmh8qr4q/download' --output '.skill-downloads/github-shipment-tracker-mmh8qr4q/SKILL.md.part' && mv '.skill-downloads/github-shipment-tracker-mmh8qr4q/SKILL.md.part' '.skill-downloads/github-shipment-tracker-mmh8qr4q/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Environment declared by the author: Requires gh CLI tool and Python 3.8+ with no additional dependencies (uses only stdlib)

Tools declared by the author (check availability in your agent): gh python3 python

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/github-shipment-tracker-mmh8qr4q/SKILL.md' && test -s '.skill-downloads/github-shipment-tracker-mmh8qr4q/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/shipment-tracker' && cp -R '.skill-downloads/github-shipment-tracker-mmh8qr4q' '.claude/skills/shipment-tracker'

Cursor
test -f '.skill-downloads/github-shipment-tracker-mmh8qr4q/SKILL.md' && test -s '.skill-downloads/github-shipment-tracker-mmh8qr4q/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/shipment-tracker' && cp -R '.skill-downloads/github-shipment-tracker-mmh8qr4q' '.cursor/skills/shipment-tracker'

Codex
test -f '.skill-downloads/github-shipment-tracker-mmh8qr4q/SKILL.md' && test -s '.skill-downloads/github-shipment-tracker-mmh8qr4q/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/shipment-tracker' && cp -R '.skill-downloads/github-shipment-tracker-mmh8qr4q' '.agents/skills/shipment-tracker'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/github-shipment-tracker-mmh8qr4q'

openskills read 'github-shipment-tracker-mmh8qr4q'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/github-shipment-tracker-mmh8qr4q/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills