Pr Trends
Generate weekly and monthly pull request trend tables for a git repository, including created PRs…
by artivilla · MIT
The skill
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:
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: trygh pr listfirst for exact PRcreatedAt,mergedAt, and line counts. Fall back togitifghis 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
Createdis grouped by PR creation time when GitHub metadata is available.Merged,Avg Days, andLines Δare grouped by merge time.- In
gitfallback mode,CreatedandAvg Daysare shown as-because local git history does not preserve complete PR lifecycle metadata.
Notes
- Run from the repo root unless
--repois 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.
Use this skill
Connect your agent to the Skill Store MCP server and ask for it by ref: artivilla/pr-trends-93077636906.
Details
- Publisher
- artivilla
- Category
- Software Development › Source control & code review
- License
- MIT
- Updated
- 2026-06-08
References
More from artivilla
- Agent Browser Automates browser interactions for web testing, form filling, screenshots, and data extraction.
- Central Station This skill should be used when the user asks about Central Station threads, community discussions…
- Chrome Devtools Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation.
- Database This skill should be used when the user wants to add a database (Postgres, Redis, MySQL, MongoDB)…