retro

Generate weekly engineering retrospectives from commit history and work patterns.

1|Updated May 5, 2026
One-click install
npx skills add https://github.com/yashs33244/my-mac-claude --skill retro-yashs33244
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/yashs33244/my-mac-claude/tree/main/skills/gstack/retro
Command: npx skills add https://github.com/yashs33244/my-mac-claude --skill retro-yashs33244

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns scattered engineering activity into a structured weekly retrospective by analyzing commit history, work patterns, and code quality signals over time.

Core Features & Use Cases

  • Weekly retrospective generation: Produces a consistent retro output that ties shipped work and development activity to measurable signals and observations.
  • Persistent history and trend tracking: Uses prior retros plus project timeline and learning logs to surface trends, not just one-week snapshots.
  • Team-aware, per-person feedback: Breaks down contributions by person and includes praise and growth areas so feedback is specific and actionable.
  • Proactive retro prompting: Supports being triggered when users ask for a weekly retro or “what did we ship,” and can suggest retro wrap-up insights at the end of the week or sprint.

Quick Start

Ask your AI to run the retro for this week and summarize what we shipped, key patterns in commits, notable code quality changes, and team-specific praise and growth areas.

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?

To generate a weekly engineering retrospective from commit history, the Skill analyzes commit and work patterns alongside code quality signals to produce structured sections. It uses stored project artifacts and prior retro markdown for trend-aware context.

What is the best way to track engineering metrics and team feedback over time?

Tracking engineering metrics and team feedback over time is done by loading persistent history from timeline.jsonl and learnings.jsonl files. The Skill surfaces trend analysis and per-person contributions rather than isolated one-week snapshots.

Can I summarize what we shipped this week using project artifacts?

You can summarize what you shipped this week by triggering the Skill with requests like 'what did we ship' or 'weekly retro'. It loads prior retro markdown, timeline.jsonl, and learnings.jsonl to analyze work patterns and highlight team contributions.

Does the weekly retro require specific filesystem files to function?

The weekly retro requires filesystem-based context loading from prior retro markdown, timeline.jsonl, and learnings.jsonl files. These files provide the project artifacts and learning logs needed for trend-aware limits and structured analysis output.

How does trend analysis work for engineering retrospectives?

Trend analysis for engineering retrospectives works by applying trend-aware limits to stored project timeline and learning logs. This approach surfaces persistent work patterns and code quality changes across multiple weeks instead of isolated single-week snapshots.