pr-retrospective

Collect merged pull request evidence and generate a Japanese retrospective learning file.

18|Updated Feb 14, 2020

Search Tags:#github #retrospective #redaction #pull-request #ci-logs #batch-branch

Ready to run

npx skills add https://github.com/subroh0508/colormaster --skill pr-retrospective

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-retrospective
Source: https://github.com/subroh0508/colormaster/tree/main/.claude/skills/pr-retrospective
Command: npx skills add https://github.com/subroh0508/colormaster --skill pr-retrospective

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a completed pull request into a complete retrospective so teams can capture what worked, what broke, and what should change next.

Core Features & Use Cases

Evidence Collection: Gather diff output, comments, reviews, CI logs, and related planning context from GitHub.
Structured Learning Output: Produce a Japanese learning document in the repository's harness format with Keep, Problem, Try, metrics, and feedback placeholders.
Batch Publication: Consolidate learning files onto a weekly batch branch so retrospectives can be reviewed and published together.
Safety and Consistency: Redact personal data and secrets, preserve idempotency, and keep the output aligned with the project's documentation rules.

Quick Start

Ask the skill to generate a retrospective for merged pull request number 123 and save the result as the matching Japanese learning file.

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 structured retrospective from a merged GitHub pull request?▼

To generate a structured retrospective from a merged GitHub pull request, request the retrospective for a specific PR number. The skill collects diffs, comments, reviews, and CI logs to produce a structured learning file.

Can I batch publish pull request retrospectives to a single branch?▼

Yes, you can batch publish pull request retrospectives. The skill consolidates generated learning files onto a weekly batch branch so teams can review and publish retrospective outputs together.

Does the retrospective output format include CI logs and code review comments?▼

Yes, the retrospective output includes CI logs and code review comments. The skill collects pull request evidence such as diffs, execution logs, and review feedback to capture what worked and what broke.

How are secrets and personal information handled in pull request retrospectives?▼

Secrets and personal information are redacted in pull request retrospectives. The skill applies safety measures to remove PII and sensitive data before publication to ensure consistent documentation.

What is the best way to document postmortems for merged pull requests automatically?▼

The best way to document postmortems for merged pull requests is using structured learning outputs. This skill transforms completed PRs into Japanese formatted retrospective files with Keep, Problem, and Try sections.

Do I need to format the retrospective output manually after generating it?▼

No, you do not need to format the retrospective output manually. The skill automatically produces a Japanese learning document aligned with the repository's documentation rules and idempotent indexing requirements.