Retro

Analyze commit history and work patterns for weekly engineering retrospectives.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/aporto-tech/aporto-agent-skills --skill retro-aporto-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Retro
Source: https://github.com/aporto-tech/aporto-agent-skills/tree/main/skills/gstack/retro
Command: npx skills add https://github.com/aporto-tech/aporto-agent-skills --skill retro-aporto-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The Retro Skill addresses the challenge of conducting weekly engineering retrospectives by providing a structured approach to analyze commit history, work patterns, and code quality metrics.

Core Features & Use Cases

  • Commit History Analysis: Reviews commit history to understand work patterns and code quality.
  • Team Awareness: Breaks down contributions by team members, offering praise and identifying growth areas.
  • Use Case: Ideal for initiating a weekly retro discussion, summarizing what was shipped, or conducting an engineering retrospective.

Quick Start

Run the Retro skill to initiate a 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 automate an engineering retrospective using commit history?

Automating an engineering retrospective with commit history involves analyzing repository commit data and work patterns to review progress and identify areas for improvement. The Retro Skill structures this by breaking down team member contributions and highlighting achievements.

What is the best way to analyze team contributions for a weekly retrospective?

Analyzing team contributions for a weekly retrospective requires reviewing commit history to understand work patterns and code quality metrics. This approach provides a structured breakdown by team members, offering praise and identifying specific growth areas.

Can I use commit history analysis to summarize what was shipped this week?

Yes, commit history analysis can summarize what was shipped by reviewing repository commit data and team member contributions. This process provides a structured summary of progress and code quality metrics to initiate a weekly retro discussion.

Do I need repository access to conduct a team work pattern analysis?

Yes, conducting a team work pattern analysis requires access to repository commit data and team member contributions. This data is essential for reviewing progress, identifying areas for improvement, and celebrating achievements during the engineering retrospective.

What should I use to structure a retro discussion around code quality metrics?

To structure a retro discussion around code quality metrics, you should use an automated retrospective approach that analyzes commit history and work patterns. This provides a structured breakdown of contributions to identify growth areas and celebrate achievements.