How do I install the Pr Trends skill?

Run npx skillmds@latest add artivilla/pr-trends in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pr Trends safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pr Trends?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pr Trends free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pr Trends?

artivilla (@artivilla) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pr Trends by artivilla — Agent Skill

Name: Pr Trends
Rating: 4.2 (5 reviews)
Author: artivilla

Pr 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 table like Created/Merged/Avg Days/Lines Δ.

artivilla Updated Sep 9, 2026

File contents

PR Trends

Use this skill when the user wants a repo-level pull request trend report.

Quick start

Run the bundled script from the target repository:

node .agents/skills/pr-trends/scripts/report-pr-trends.mjs

Useful options:

node .agents/skills/pr-trends/scripts/report-pr-trends.mjs --repo /path/to/repo
node .agents/skills/pr-trends/scripts/report-pr-trends.mjs --mode gh
node .agents/skills/pr-trends/scripts/report-pr-trends.mjs --mode git

Source selection

--mode auto: try gh pr list first for exact PR createdAt, mergedAt, and line counts. Fall back to git if gh is unavailable or offline.
--mode gh: require GitHub CLI data. Use this when the user needs exact PR creation trends and accurate days-to-merge.
--mode git: use only local mainline history. This gives reliable merged counts and merged lines changed, but it cannot recover exact PR creation timestamps or closed-unmerged PRs.

Output

The script prints:

A weekly summary table
A monthly summary table
A short note describing which data source was used

Interpretation

Created is grouped by PR creation time when GitHub metadata is available.
Merged, Avg Days, and Lines Δ are grouped by merge time.
In git fallback mode, Created and Avg Days are shown as - because local git history does not preserve complete PR lifecycle metadata.

Notes

Run from the repo root unless --repo is provided.
The script reads first-parent history so the report reflects the mainline branch.
If the fallback note mentions missing PR numbers, treat those as likely closed, unmerged, or otherwise not reconstructable from local git alone.

---name: pr-trendsdescription: 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 table like Created/Merged/Avg Days/Lines Δ.--- # PR Trends Use this skill when the user wants a repo-level pull request trend report. ## Quick start Run the bundled script from the target repository: ```bash node .agents/skills/pr-trends/scripts/report-pr-trends.mjs ``` Useful options: ```bash node .agents/skills/pr-trends/scripts/report-pr-trends.mjs --repo /path/to/repo node .agents/skills/pr-trends/scripts/report-pr-trends.mjs --mode gh node .agents/skills/pr-trends/scripts/report-pr-trends.mjs --mode git ``` ## Source selection - `--mode auto`: try `gh pr list` first for exact PR `createdAt`, `mergedAt`, and line counts. Fall back to `git` if `gh` is unavailable or offline. - `--mode gh`: require GitHub CLI data. Use this when the user needs exact PR creation trends and accurate days-to-merge. - `--mode git`: use only local mainline history. This gives reliable merged counts and merged lines changed, but it cannot recover exact PR creation timestamps or closed-unmerged PRs. ## Output The script prints: 1. A weekly summary table 2. A monthly summary table 3. A short note describing which data source was used ## Interpretation - `Created` is grouped by PR creation time when GitHub metadata is available. - `Merged`, `Avg Days`, and `Lines Δ` are grouped by merge time. - In `git` fallback mode, `Created` and `Avg Days` are shown as `-` because local git history does not preserve complete PR lifecycle metadata. ## Notes - Run from the repo root unless `--repo` is provided. - The script reads first-parent history so the report reflects the mainline branch. - If the fallback note mentions missing PR numbers, treat those as likely closed, unmerged, or otherwise not reconstructable from local git alone.

Frequently asked questions