Agent skill · Code Review & Quality

review-metrics

Analyze team code review activity and performance metrics from GitHub PRs. Use when: (1) User asks about team review statistics or performance, (2) User wants to see who reviewed what PRs, (3) User asks about review response times or approval rates, (4) User mentions "review metrics", "review stats", "review activity", or "レビュー分析", (5) User asks about review bottlenecks, stuck PRs, or review load.

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill review-metrics --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: none
Allowed tools: -Bash
Path: skills/analysis/review-metrics/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Review Metrics Collect and analyze team review metrics from GitHub pull requests. ## Invocation Run via the unified dispatch script: ```bash ../../scripts/dispatch.sh $0 $1 ``` Where `$0` is the period (default: `week`) and `$1` is the command. If no command is provided, all rankings are shown. ## Examples | Command | Dispatch | |---------|----------| | `/review-metrics` | `../../scripts/dispatch.sh week` | | `/review-metrics last-week` | `../../scripts/dispatch.sh last-week` | | `/review-metrics month comments` | `../../scripts/dispatch.sh month comments` | | `/review-metrics last-week response-time` | `../../scripts/dispatch.sh last-week response-time` | | `/review-metrics last-week fix-time` | `../../scripts/dispatch.sh last-week fix-time` | | `/review-metrics last-week bottleneck` | `../../scripts/dispatch.sh last-week bottleneck` | | `/review-metrics stuck` | `../../scripts/dispatch.sh week stuck` | | `/review-metrics last-week reviewer-load` | `../../scripts/dispatch.sh last-week reviewer-load` | | `/review-metrics last-week cycles` | `../../scripts/dispatch.sh last-week cycles` | | `/review-metrics last-week pr-size` | `../../scripts/dispatch.sh last-week pr-size` | ## Ava

What's inside
Steps it walks through
  1. Invocation
  2. Examples
  3. Available Scripts
  4. Ranking Scripts (Top 3)
  5. Analysis Scripts (Team-wide)
  6. Period Options
  7. Metrics Collected
  8. Rankings
  9. Analysis
  10. Requirements
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the review-metrics skill do?

Analyze team code review activity and performance metrics from GitHub PRs. Use when: (1) User asks about team review statistics or performance, (2) User wants to see who reviewed what PRs, (3) User asks about review response times or approval rates, (4) User mentions "review metrics", "review stats", "review activity", or "レビュー分析", (5) User asks about review bottlenecks, stuck PRs, or review load.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill review-metrics --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going