skills.rest
yocxy2
yocxy2COMMUNITY
Explore all skills by this author →
GitHub

retro

Analyze commit history and work patterns to generate engineering retrospective reports.

Updated Jul 26, 2026
Search Tags:#git#analytics#productivity#retrospective#engineering#team-management
One-click install
npx skills add https://github.com/yocxy2/gstack3 --skill retro-yocxy2
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/yocxy2/gstack3/tree/main/retro
Command: npx skills add https://github.com/yocxy2/gstack3 --skill retro-yocxy2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the difficulty of manually tracking engineering progress, team contributions, and project learnings by automating the generation of retrospective reports.

Core Features & Use Cases

  • Trend Tracking: Analyzes commit history and work patterns to identify velocity and quality trends over time.
  • Team Insights: Breaks down contributions by individual, highlighting both praise-worthy achievements and areas for growth.
  • Use Case: At the end of a sprint, use this Skill to generate a comprehensive summary of what was shipped, which team members contributed most, and what lessons were learned from recent timeline events.

Quick Start

Invoke the retro skill to generate a weekly engineering retrospective based on the current project history.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate an engineering retrospective from git commit history?▼

Generating an engineering retrospective from git commit history involves analyzing commit patterns and work velocity to produce a comprehensive summary report of team contributions and project trends.

What is an automated engineering retrospective and how does it work?▼

An automated engineering retrospective analyzes commit history and work patterns to identify velocity trends, generating per-person contribution breakdowns and performance tracking reports for team-based software development.

Can I track individual team member contributions for a sprint retrospective?▼

Yes, you can track individual team member contributions for a sprint retrospective by analyzing commit history to highlight specific achievements and identify areas for growth on a per-person basis.

Does automated retrospective reporting work for team-based software development environments?▼

Automated retrospective reporting is designed for team-based software development environments, applying commit history analysis to satisfy requirements for persistent history tracking and trend analysis.

What's the best way to analyze engineering work patterns for performance tracking?▼

The best way to analyze engineering work patterns for performance tracking is automating commit history analysis to identify velocity and quality trends, generating consistent growth feedback and contribution breakdowns.

When do I need automated engineering retrospective reports?▼

You need automated engineering retrospective reports at the end of a sprint or when requiring consistent performance tracking, to summarize shipped work, team contributions, and lessons learned from timeline events.

Related Skills

Explore More Software Engineering Skills→
KrismithReddy12KrismithReddy12

gstack-openclaw-retro

Analyze git commit history to generate engineering retrospectives and team performance metrics.

Community
Advanced
fabioc-alohafabioc-aloha
1

status-reporting

Generate stakeholder-friendly project status updates from technical progress.

Community
Intermediate
smarmen86smarmen86

retro

Generates engineering retrospectives from git commit history and timeline events.

Community
Advanced
webrix-aiwebrix-ai
1

performance-reviews

Coordinate performance review cycles with BambooHR and Slack MCPs.

Official
Advanced