skills/pr-trends/SKILL.md
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 Δ.
npx skillsauth add artivilla/agents-config pr-trendsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill when the user wants a repo-level pull request trend report.
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
--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.The script prints:
Created is grouped by PR creation time when GitHub metadata is available.Merged, Avg Days, and Lines Δ are grouped by merge time.git fallback mode, Created and Avg Days are shown as - because local git history does not preserve complete PR lifecycle metadata.--repo is provided.development
Review UI code against Vercel's Web Interface Guidelines. Use when checking interactions, animation, layout, content, accessibility, performance, and design standards with MUST/SHOULD/NEVER rules.
development
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
development
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
development
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.