pr-retrospective

Generates structured retrospectives for merged PRs and suggests improvements.

Updated May 15, 2026
One-click install
npx skills add https://github.com/heyu-ai/yibi-stack --skill pr-retrospective-heyu-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-retrospective
Source: https://github.com/heyu-ai/yibi-stack/tree/main/plugins/pr-flow/skills/pr-retrospective
Command: npx skills add https://github.com/heyu-ai/yibi-stack --skill pr-retrospective-heyu-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The pr-retrospective Skill solves the issue of manually compiling and documenting the insights from PR retrospectives, providing a structured way to capture learnings and identify areas for improvement.

Core Features & Use Cases

  • Automated Retrospective Generation: Automatically generates a structured retrospective based on the PR context.
  • Lesson Identification: Identifies lessons learned and suggests potential actions for improvement.
  • Rule Generation: Suggests rules to be added to the CLAUDE.md file to prevent future issues.
  • Use Case: After a PR is merged, the Skill can be used to automatically create a retrospective, highlighting the problems solved, the value delivered, and the lessons learned.

Quick Start

Run the pr-retrospective Skill on a merged PR to generate a retrospective and receive recommendations for improvement.

Frequently Asked Questions about pr-retrospective

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

FAQPage Schema
How do I generate a retrospective for a merged GitHub PR?

To generate a retrospective for a merged PR, run the pr-retrospective Skill to automatically extract context, identify lessons learned, and document structured insights for future improvement.

What is an AI-driven PR retrospective and how does it work?

An AI-driven PR retrospective automatically analyzes merged pull requests to identify solved problems, delivered value, and lessons learned, then suggests actionable rules to prevent future issues.

Do I need GitHub CLI installed to automate PR retrospective generation?

Yes, automating PR retrospective generation requires GitHub access and the GitHub CLI (gh) installed, along with Python and jq, to fetch PR data and process insights.

Can I automatically update CLAUDE.md with rules from a pull request retrospective?

Yes, the retrospective generation process suggests specific rules to add to your CLAUDE.md file, helping prevent similar issues in future development cycles.

What's the best way to capture lessons learned after merging a pull request?

The best way to capture lessons learned is using an automated retrospective tool that analyzes the merged PR context and outputs structured documentation of problems solved and improvement recommendations.

Why does the PR retrospective process require the yibi-stack repository?

The PR retrospective process requires the yibi-stack Skill repository to be installed because it provides the foundational scripts and references needed to execute the retrospective generation workflow.