retro

Analyze commit history and work patterns to generate weekly engineering retrospectives.

Updated Dec 22, 2019
One-click install
npx skills add https://github.com/sajalsuhane/sajalsuhane.github.io --skill retro-sajalsuhane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/sajalsuhane/sajalsuhane.github.io/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/sajalsuhane/sajalsuhane.github.io --skill retro-sajalsuhane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives enable teams to reflect on weekly work by aggregating commit history, work patterns, and code quality metrics into a structured retrospective with praise and growth insights.

Core Features & Use Cases

  • Team-aware retrospectives: breaks down per-person contributions to highlight praise and growth areas.
  • Per-period analysis: supports time windows (7d, 24h, etc.) and cross-project global retros.
  • Operational guidance: outputs actionable recommendations for process improvements.

Quick Start

Run the retro with a window like /retro 7d and Claude will fetch data, compute metrics, and present a narrative.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate a weekly engineering retrospective from commit history?

Generate a weekly engineering retrospective by running the retro command with a time window like 7d. It analyzes project commit history and work patterns to compute code quality metrics, summarize contribution activity, and output a structured narrative with actionable recommendations.

Can I run a retrospective for a specific time window other than a week?

Yes, retrospectives support custom time windows such as 24h or 7d. You can specify the desired period when running the command to analyze commit history and work patterns within that exact timeframe, generating per-person praise and growth insights.

Does the retrospective analysis break down contributions by individual team members?

Yes, team-aware retrospectives break down per-person contributions. The analysis highlights specific praise and growth areas for each developer based on their commit activity and code quality metrics within the specified timeframe.

What level of insights does an engineering retrospective provide for technical leadership?

Engineering retrospectives present a clear narrative tailored for a CTO-level audience. Insights include code quality trends, contribution activity, hotspots, and actionable recommendations for process improvements, customized to the requesting user's perspective.

Can I analyze work patterns across multiple projects in a single retrospective?

Yes, the retrospective supports cross-project global retros. This allows you to aggregate commit history, work patterns, and code quality metrics across multiple projects into a unified weekly retrospective summary.