retro

Name: retro
Availability: InStock
Author: Manzueti

Generate engineering retrospective reports from commit history and work patterns.

Updated Jun 4, 2026

Search Tags:#code quality #commit history #team analysis #retro #work pattern

Ready to run

npx skills add https://github.com/Manzueti/cyberdart --skill retro-manzueti

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/Manzueti/cyberdart/tree/main/retro
Command: npx skills add https://github.com/Manzueti/cyberdart --skill retro-manzueti

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of conducting weekly engineering retrospectives, analyzing commit history, work patterns, and code quality metrics with persistent history and trend tracking.

Core Features & Use Cases

Commit History Analysis: Automatically analyzes commit history to identify patterns and trends.
Work Pattern Tracking: Tracks individual contributions and identifies areas for growth.
Team Awareness: Breaks down contributions per person with praise and growth areas.
Use Case: Use this Skill at the end of a work week or sprint to review the team's progress and identify areas for improvement.

Quick Start

Run the retro skill to generate a weekly engineering retrospective report.

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 using commit history?▼

Automate engineering retrospectives by running a script that analyzes commit history and work patterns to generate weekly reports, tracking team contributions and identifying growth areas. You need access to commit history and project files.

What is commit history analysis for tracking team work patterns?▼

Commit history analysis for tracking work patterns involves parsing commit logs to identify individual contributions, detect trends, and highlight areas for improvement. It provides persistent history tracking for weekly engineering reviews.

Can I generate a weekly retrospective report for individual team contributions?▼

Yes, you can generate a weekly retrospective report that breaks down individual team contributions. The analysis highlights praise areas and specific growth opportunities per person based on their commit history.

Do I need project files access to analyze code quality metrics for a sprint review?▼

Yes, you need access to both commit history and project files to analyze code quality metrics. This access allows the tool to evaluate work patterns and generate an accurate retrospective report for your sprint review.

When should I run an automated retrospective analysis for my engineering team?▼

Run an automated retrospective analysis at the end of a work week or sprint. This timing allows you to review the team's recent progress, assess code quality metrics, and identify areas for improvement before the next cycle.

What are the limitations of using commit history for team contribution analysis?▼

Commit history analysis limitations include relying solely on commit data to evaluate contributions, which may miss pair programming or non-code work. It requires comprehensive project file access to accurately assess code quality metrics.