retro

Generates weekly engineering retrospectives from Git commit history and code metrics.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Vinnni002/Sikshak --skill retro-vinnni002
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/Vinnni002/Sikshak/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/Vinnni002/Sikshak --skill retro-vinnni002

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the generation of weekly engineering retrospectives, providing deep insights into team performance, code quality, and individual contributions.

Core Features & Use Cases

  • Automated Data Analysis: Gathers and analyzes commit history, work patterns, and code quality metrics.
  • Team-Aware Insights: Breaks down per-person contributions, highlighting praise and growth areas.
  • Trend Tracking: Persistent history and trend analysis for continuous improvement.
  • Use Case: Run /retro at the end of each week to get a comprehensive overview of your team's development velocity, identify bottlenecks, and celebrate successes.

Quick Start

Run the retro skill to analyze the last 7 days of commits.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I automate engineering retrospectives from Git commit history?

Automating engineering retrospectives involves analyzing Git commit history, work patterns, and code quality metrics to generate comprehensive weekly reports. The tool aggregates commit data to provide team-aware insights into per-person contributions and development velocity.

How do I track developer productivity and team performance using commit analysis?

Tracking developer productivity through commit analysis involves parsing Git logs to measure individual contributions and identify growth areas. The tool performs time zone conversions and data aggregation to deliver persistent history and trend tracking for continuous team improvement.

What is the best way to generate weekly code quality metrics for a development team?

Generating weekly code quality metrics is best handled by running a retrospective command at the end of each week. This automatically analyzes the last 7 days of commits, identifies bottlenecks, and highlights praise and growth areas for continuous improvement.

Can I analyze individual developer contributions and work patterns from a Git repository?

Yes, you can analyze individual developer contributions from a Git repository. The retrospective tool breaks down per-person commits and work patterns, utilizing Git commands and time zone conversions to provide detailed, team-aware insights into individual performance.

Does automated retrospective reporting require external dependencies or specific platforms?

Automated retrospective reporting operates with no external dependencies. It relies solely on Git commands to gather commit history and work pattern data, performing time zone conversions and data aggregation directly to generate detailed reports.

How does trend tracking work for continuous engineering team improvement?

Trend tracking for continuous improvement works by storing persistent history of weekly engineering retrospectives. By comparing aggregated commit data and code quality metrics over time, teams can visualize development velocity changes and track growth areas across iterations.