skills.rest
fumtas1k
fumtas1kCOMMUNITY
Explore all skills by this author →
GitHub

retro

Analyze merged pull requests and generate documentation improvement PRs.

Updated Apr 11, 2026
Search Tags:#code review#PR analysis#automated documentation#documentation improvement#post-mortem analysis
One-click install
npx skills add https://github.com/fumtas1k/devtools --skill retro-fumtas1k
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/fumtas1k/devtools/tree/main/.agents/skills/retro
Command: npx skills add https://github.com/fumtas1k/devtools --skill retro-fumtas1k

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of analyzing post-merge PRs to extract actionable insights and generate documentation improvement PRs, saving developers time and effort in the documentation process.

Core Features & Use Cases

  • PR Analysis: Extracts insights from merged PRs, including issues, lessons learned, and areas for improvement.
  • Documentation Improvement: Generates PRs with suggested changes to documentation based on the insights.
  • Use Case: After merging a PR, the Skill can automatically identify common issues and suggest PRs to improve the documentation, reducing the need for manual review.

Quick Start

Run /retro to automatically analyze the last merged PR and generate a documentation improvement PR.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I automate post-merge PR analysis for documentation improvements?▼

Automated PR post-mortem analysis processes merged pull requests to extract actionable insights and generates new PRs with suggested documentation improvements. It categorizes findings into preventable issues by processing review comments and conversation history.

What is a PR post-mortem analysis and how does it improve code review documentation?▼

PR post-mortem analysis evaluates merged pull requests to extract lessons learned and identify preventable issues. It processes existing review comments and conversation history to generate actionable documentation improvements, reducing the need for manual post-merge review.

How do I generate documentation update PRs from review comments automatically?▼

You can generate documentation PRs by running the retro command. This analyzes the last merged PR, categorizes findings from review comments into preventable issues, and automatically suggests a documentation improvement PR.

Can I extract lessons learned from conversation history after merging a pull request?▼

Yes, this Skill processes conversation history and existing lessons from merged PRs to extract actionable insights. It categorizes these findings to generate targeted documentation updates automatically.

Does automated documentation improvement work without external dependencies?▼

Yes, this Skill operates with no external dependencies. It runs independently to analyze merged PRs, process review comments, and generate documentation improvement PRs directly within your workflow.

Related Skills

Explore More Software Engineering Skills→
ulises-jeremiasulises-jeremias
2

gh-address-comments

Automate processing and responding to GitHub pull request comments via gh CLI.

Community
Basic
harshitsinghbhandariharshitsinghbhandari
2

pr-learning

Extract actionable learnings from merged PR lifecycles with evidence.

Community
Advanced
strawgatestrawgate

follow-the-pr

Monitor GitHub pull request states for CI changes, reviews, and merge readiness.

Community
Advanced
tubone24tubone24
4

mspec-archive

Merge changes into the source-of-truth spec and archive them.

Community
Advanced