pm-sprint-review

Generate sprint retrospective reports from GitHub PRs and issues.

3|1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/auerbachb/claude-code-config --skill pm-sprint-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-sprint-review
Source: https://github.com/auerbachb/claude-code-config/tree/main/.claude/skills/pm-sprint-review
Command: npx skills add https://github.com/auerbachb/claude-code-config --skill pm-sprint-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) components.

What problem does it solve?

Generate a clear, data-driven sprint retrospective without manual GitHub queries or spreadsheet assembly by automatically collecting merged PRs, closed issues, cycle times, review cycles, blockers, and per-contributor metrics for a defined time window.

Core Features & Use Cases

  • Automated data gathering: Aggregates merged PRs, closed issues, PR bodies, review events, and issue events via GitHub CLI to build a complete picture of sprint activity.
  • Velocity and quality metrics: Computes throughput, average and median cycle time, review cycles per PR, code volume, and slipped work to quantify team performance.
  • Blocker and contributor analysis: Identifies long-lived PRs, stalled issues, dependency blockers, and produces per-contributor breakdowns and constructive recommendations for the next sprint.

Quick Start

Run the pm-sprint-review skill with an optional --days N argument to produce a retrospective for the past N days (default 14).

Frequently Asked Questions about pm-sprint-review

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

FAQPage Schema
How do I generate a sprint retrospective report from GitHub PRs and issues?

A sprint retrospective report summarizes merged PRs, closed issues, and velocity metrics by querying the GitHub API. It provides a data-driven review of sprint activity, blockers, and per-contributor performance without manual spreadsheet assembly.

What metrics are included in an automated sprint velocity report?

Automated sprint velocity reports compute throughput, average and median cycle time, review cycles per PR, code volume, and slipped work. These metrics quantify team performance and identify long-lived PRs or stalled issues.

Do I need GitHub CLI to calculate cycle time and review metrics?

Yes, calculating cycle time and review metrics requires GitHub CLI access. Local helper scripts query the GitHub API via the CLI to fetch PR bodies, review events, and issue activity for metric computation.

Can I analyze GitHub repository activity for a custom time window?

Yes, you can analyze GitHub repository activity for a custom time window by specifying the number of days. The default review window is 14 days, but you can adjust this to capture sprint activity over any period.

How do I identify blockers and stalled issues in my GitHub sprint?

Identifying blockers and stalled issues in a GitHub sprint involves analyzing issue events and PR lifespans. The tool detects long-lived PRs, dependency blockers, and stalled issues to highlight work impeding sprint progress.

What is the best way to automate per-contributor breakdowns for a sprint review?

Automating per-contributor breakdowns for a sprint review is best done using scripts that query the GitHub API. This approach aggregates individual contributions, review cycles, and code volume to produce constructive recommendations.