retro

Aggregate commit history and code quality metrics into weekly engineering retrospectives.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/VertaKhan/cs_gstack --skill retro-vertakhan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/VertaKhan/cs_gstack/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/VertaKhan/cs_gstack --skill retro-vertakhan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to extract actionable learning from dense commit histories. The retro skill compiles contributions, patterns, and code-quality signals into a concise weekly narrative that surfaces praise and growth areas.

Core Features & Use Cases

  • Per-person contribution breakdown with praise and growth suggestions.
  • Persistent history and trend tracking to measure improvements over time.
  • Team-aware narrative suitable for sprint retros and planning discussions.

Quick Start

Run the retro skill with /retro to generate a team-wide weekly engineering retrospective.

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 git commit history?

To generate a weekly engineering retrospective from git history, you need a tool that aggregates commit patterns and code quality metrics into a narrative. This skill compiles team contributions into a concise review with praise and growth areas.

What is the best way to track team performance and code quality metrics over time?

Tracking team performance and code quality metrics over time requires persistent history and trend analysis. This skill maintains long-term historical data to measure improvements and highlight strengths across a weekly cycle.

How do I get per-person contribution breakdowns for a sprint retrospective?

Getting per-person contribution breakdowns for sprint retros involves analyzing individual work patterns from commit data. This skill provides personalized feedback with actionable growth suggestions for each team member.

Can I use commit history analysis to produce actionable growth suggestions for my engineering team?

Yes, using commit history analysis to produce actionable growth suggestions helps teams extract learning from dense logs. This skill surfaces specific opportunities for improvement suitable for planning discussions.

Does this engineering retrospective tool require any external dependencies to run?

No external dependencies are required to run this engineering retrospective tool. It operates independently to aggregate work patterns and export a narrative plus recommendations for your review sessions.

How do I prepare for a sprint retro using team-wide contribution data?

Preparing for a sprint retro using team-wide contribution data requires aggregating recent work patterns into a readable format. This skill exports a team-aware narrative that surfaces praise and growth areas for review sessions.