retro

Analyze session transcripts and GitHub PR/CI history to propose MD-file edits.

Updated Mar 30, 2026

Search Tags:#CI/CD #retrospective #GitHub #engineering cycle #MD-file edit

Ready to run

npx skills add https://github.com/weside-ai/claude-code-plugin --skill retro-weside-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/weside-ai/claude-code-plugin/tree/main/we/skills/retro
Command: npx skills add https://github.com/weside-ai/claude-code-plugin --skill retro-weside-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, claude-plugin, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill systematically reviews the recent engineering cycle, identifying and addressing frictions found in transcripts and GitHub API data.

Core Features & Use Cases

Retrospective Analysis: Analyzes transcripts and GitHub data to find frictions and propose fixes.
Proposal Placement: Suggests where to place MD-file edits to prevent future occurrences.
User Approval: Applies only what the user approves, with per-item [y/n] gates.
Logging: Logs the retro run for future pattern detection.

Quick Start

Run the retro skill by typing "/we:retro".

Frequently Asked Questions about retro

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

FAQPage Schema

How do I conduct an engineering cycle retrospective using GitHub PR and CI history?▼

An engineering cycle retrospective analyzes session transcripts and GitHub PR/CI history to identify frictions. It requires gh auth for data access and proposes MD-file edits to prevent recurring issues.

How do I automate retrospective analysis of CI/CD pipelines and session transcripts?▼

Automated retrospective analysis reviews session transcripts alongside GitHub API data to pinpoint engineering frictions. It then logs the findings and suggests targeted MD-file edits for future prevention.

Do I need GitHub CLI authentication to analyze PR history for a sprint retrospective?▼

Yes, you need gh auth configured to access GitHub PR and CI history data. The retrospective analysis also requires a Claude plugin environment to execute the systematic review process.

Can I review and approve individual engineering cycle fixes during a retrospective?▼

Yes, the retrospective process applies fixes only through per-item user approval gates. You can selectively accept or decline each proposed MD-file edit generated from the transcript and GitHub analysis.

What is the best way to track recurring engineering frictions across multiple CI/CD cycles?▼

Logging retrospective findings from each engineering cycle enables future pattern detection. By systematically recording frictions found in GitHub and transcript data, you can identify and address recurring workflow issues.

How to generate MD-file edits to prevent engineering bottlenecks identified in a retrospective?▼

To generate preventive MD-file edits, analyze session transcripts and GitHub CI/CD history to find frictions. The retrospective then proposes specific documentation edits, which are applied only after user approval.