skills.rest
zoraxl
zoraxlCOMMUNITY
Explore all skills by this author →
GitHub

pr-score-log

Extract numeric review scores from merged GitHub pull requests into a markdown table.

3|Updated Apr 27, 2026
Search Tags:#automation#github#metrics#reporting#code-review#pull-request
One-click install
npx skills add https://github.com/zoraxl/team-brain --skill pr-score-log
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-score-log
Source: https://github.com/zoraxl/team-brain/tree/main/.cursor/skills/pr-score-log
Command: npx skills add https://github.com/zoraxl/team-brain --skill pr-score-log

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq.

What problem does it solve?

This skill solves the difficulty of manually tracking and aggregating performance metrics from pull request reviews, providing a clear, historical view of PR scores.

Core Features & Use Cases

  • Automated Aggregation: Scans merged pull requests to extract numeric scores from review comments.
  • Formatted Reporting: Generates a clean, ready-to-paste markdown table containing PR links, scores, and merge dates.
  • Use Case: Use this when you need to generate a performance report for a team sprint or review cycle by listing all merged PRs since a specific PR number.

Quick Start

Ask the agent to generate a table of merged PR scores for all pull requests after number 123.

Frequently Asked Questions about pr-score-log

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract numeric review scores from merged GitHub pull requests?▼

You can generate a markdown table of merged PR scores by scanning merged pull requests and extracting numeric scores from their bodies. This requires GitHub CLI and jq to parse repository metadata and PR content into a structured format.

Can I track development velocity using GitHub pull request metrics?▼

You can track development velocity by aggregating numeric review scores from merged pull requests into a historical markdown table. This provides a clear view of PR scores and merge dates for performance reporting.

Do I need GitHub CLI and jq to generate pull request score reports?▼

Yes, you need GitHub CLI and jq installed to parse repository metadata and PR body content. These dependencies are required to extract numeric scores from merged pull requests and format them into a markdown table.

How do I list all merged PRs since a specific pull request number?▼

You can list all merged PRs since a specific pull request number by asking an agent to generate a table of merged PR scores. The tool scans merged pull requests after that number and extracts scores into a markdown table.

What is the best way to automate code review performance reporting for a sprint?▼

The best way to automate code review performance reporting is to scan merged pull requests and extract numeric review scores from their bodies into a ready-to-paste markdown table. This facilitates historical analysis of development velocity across repository pull requests.

Related Skills

Explore More Software Engineering Skills→
rawvegrawveg
40

github-issue-fetcher

Fetch GitHub issues from the current repository using gh and jq.

Community
Advanced
brand6brand6

retrospective

Extract sprint data into a structured markdown retrospective with actionable improvements.

Community
Advanced
mkikenmkiken
1

pr-body

Generate GitHub pull request body content from gh commands and diff analysis.

Community
Intermediate
auerbachbauerbachb
3

pm-sprint-review

Generate sprint retrospective reports from GitHub PRs and issues.

Community
Advanced