retro

Analyze commit history and work patterns for engineering retrospectives.

Updated Mar 27, 2026

Search Tags:#code quality #commit analysis #team metrics #work patterns #trend tracking

Ready to run

npx skills add https://github.com/BaGyun0107/harness-starterkit --skill retro-bagyun0107

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/BaGyun0107/harness-starterkit/tree/main/.agents/skills/gstack-retro
Command: npx skills add https://github.com/BaGyun0107/harness-starterkit --skill retro-bagyun0107

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps engineering teams analyze their work patterns and commit history to improve productivity and identify areas for growth.

Core Features & Use Cases

Work Pattern Analysis: Examines commit history and work habits over time to reveal trends.
Team-aware Metrics: Breaks down contributions per person, highlighting praise and growth opportunities.
Use Case: When a team leader asks "what did we ship last week," this Skill provides a comprehensive retrospective report.

Quick Start

Run the retro skill in your project directory to generate the weekly engineering report based on your Git history.

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 commit history, run the analysis tool directly in your project directory to extract work patterns, team contributions, and code quality metrics automatically.

What is commit analysis for tracking team work patterns and project trends?▼

Commit analysis for tracking team work patterns involves examining commit history over time to reveal development trends, measure code quality, and break down individual contributions for engineering retrospectives.

Can I track individual developer contributions and code quality metrics for my team?▼

Yes, you can track individual developer contributions and code quality metrics. The analysis breaks down contributions per person, highlighting both team praise and specific growth opportunities based on commit history.

Do I need any external dependencies to analyze project trends for engineering retrospectives?▼

No external dependencies are required to analyze project trends for engineering retrospectives. You can run the analysis directly within your project environment to track persistent history and generate team-specific insights.

When do I need trend tracking and work pattern analysis for development progress?▼

You need trend tracking and work pattern analysis when reviewing weekly development progress, evaluating team contributions, or identifying areas for growth and productivity improvements during project retrospectives.