skills.rest
jasonmichaelbell78-creator
jasonmichaelbell78-creatorCOMMUNITY
Explore all skills by this author →
GitHub

pr-retro

Generate structured retrospectives for PR review cycles with action-item tracking.

Updated Feb 24, 2026
Search Tags:#retrospective#dashboard#pr#workflow-automation#code-review#team-process#tdms
One-click install
npx skills add https://github.com/jasonmichaelbell78-creator/framework --skill pr-retro-jasonmichaelbell78-creator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-retro
Source: https://github.com/jasonmichaelbell78-creator/framework/tree/main/.claude/skills/pr-retro
Command: npx skills add https://github.com/jasonmichaelbell78-creator/framework --skill pr-retro-jasonmichaelbell78-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR review cycles often lack structured, actionable retrospectives that help teams learn and improve. This Skill provides a comprehensive, actionable retrospective for completed PRs, surfacing key findings and improvement opportunities.

Core Features & Use Cases

  • Full retro generation for a PR, including all mandatory sections
  • Dashboard mode to surface merged PRs missing retros
  • Per-round breakdown with files touched and outcomes
  • Cross-PR systemic analysis and TDMS integration
  • Action-item auditing and follow-up tracking

Quick Start

Invoke /pr-retro with a PR number to generate a single-PR retrospective, or run /pr-retro with no args to view the missing retros dashboard.

Frequently Asked Questions about pr-retro

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

FAQPage Schema
How do I generate a structured retrospective for a merged pull request?▼

Generate a PR retrospective by providing a pull request number, which produces a full analysis with per-round review data, files touched, and tracked action items. This surfaces key findings and improvement opportunities for the team.

What is the best way to find merged pull requests missing retrospectives across a dashboard?▼

Run the retrospective tool with no arguments to activate dashboard mode, which surfaces all merged pull requests lacking a structured retro. This cross-PR view helps identify gaps in team process coverage.

Can I track action items and systemic patterns from code review cycles across multiple PRs?▼

Yes, the tool performs cross-PR systemic analysis to identify recurring workflow patterns and audits action-item follow-ups. It integrates with the TDMS debt system to track technical debt arising from reviews.

Does a pull request retrospective include a breakdown of individual review rounds?▼

Yes, the retrospective provides a per-round breakdown detailing files touched and outcomes for each review cycle. This granular data helps teams understand specific friction points within the code review process.

How do code review retrospectives improve team workflow automation?▼

Retrospectives surface actionable findings from the review cycle, enabling teams to identify bottlenecks and track follow-up action items. This structured feedback loop directly informs and improves ongoing team workflow automation processes.

Related Skills

Explore More Software Engineering Skills→
auerbachbauerbachb
3

pm-rate-team

Evaluate GitHub contributor metrics and CodeRabbit review outcomes over a configurable time window.

Community
Advanced
GDSDNGDSDN
3

qa-backlog-add-followup

Create prioritized, tagged QA follow-up items linked to project backlog stories.

Community
Intermediate
bajajvinamrbajajvinamr

retro

Analyze commit history and work patterns to generate weekly engineering retrospectives.

Community
Advanced
auldsyababuaauldsyababua
6

data-analyst

Automate missing-value analysis, imputation, and Plotly Dash dashboard generation for CSV datasets.

Community
Advanced