workflow-retrospective

Analyzes completed PRs and git history to generate categorized improvement opportunities.

9|Updated Feb 22, 2026

Search Tags:#workflow #retrospective #quality-assurance #process-improvement #git-history #pr-analysis

Ready to run

npx skills add https://github.com/lhpaul/ai-dev-framework-template --skill workflow-retrospective-lhpaul

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workflow-retrospective
Source: https://github.com/lhpaul/ai-dev-framework-template/tree/main/.codex/skills/workflow-retrospective
Command: npx skills add https://github.com/lhpaul/ai-dev-framework-template --skill workflow-retrospective-lhpaul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes completed work items (PRs, batches, or releases) to surface bottlenecks, gaps, and actionable improvements that prevent recurrence and accelerate future delivery.

Core Features & Use Cases

Collects PR metadata (review cycles, labels, merge status) and git history to surface trends and improvement opportunities.
Generates categorized opportunities with severity and actionable next steps, including options to address now, add to backlog, or skip.
Supports on-demand scope by PR number, branch name, or date to enable targeted retrospectives.

Quick Start

Ask your agent to run a retrospective on the most recently completed PR.

Frequently Asked Questions about workflow-retrospective

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

FAQPage Schema

How do I analyze PR metadata and git history for a retrospective?▼

To analyze PR metadata and git history for a retrospective, this skill automates the collection of review cycles, labels, and merge status from completed work batches, branches, or date-scoped releases to surface process improvement opportunities.

What is the best way to identify process bottlenecks in completed pull requests?▼

The best way to identify process bottlenecks in completed pull requests is to run an automated retrospective analysis. It surfaces gaps and trends from PR metadata and git history, generating categorized opportunities with severity and actionable next steps to prevent recurrence.

Can I run a retrospective analysis scoped to a specific branch or date range?▼

Yes, you can run a retrospective analysis scoped to a specific branch or date range. The skill supports on-demand scope by PR number, branch name, or date, enabling targeted reviews across recent contributions or specific time windows.

How does a git history analysis help with continuous process improvement?▼

A git history analysis helps with continuous process improvement by surfacing trends and bottlenecks from completed work items. It generates categorized opportunities with severity and actionable next steps, allowing teams to address issues now, add them to the backlog, or skip them.

Do I need to manually collect review cycle data before running a PR retrospective?▼

No, you do not need to manually collect review cycle data before running a PR retrospective. The skill satisfies data collection requirements for PR metadata, review cycles, labels, and git history automatically to drive improvements.