retro

Analyze commit history and code quality metrics to generate weekly team retrospectives.

Updated Apr 5, 2026

Search Tags:#engineering #history #code-quality #team #retro

Ready to run

npx skills add https://github.com/GTC6244/ToolBridge --skill retro-gtc6244

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/GTC6244/ToolBridge/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/GTC6244/ToolBridge --skill retro-gtc6244

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives are hard to assemble from scattered notes. This Skill analyzes commit history, work patterns, and code quality metrics to provide a persistent, team-aware retrospective that highlights praise and growth areas.

Core Features & Use Cases

Automated weekly retrospection: aggregates contributions, blockers, and impact across the team.
Team-aware insights: breaks down per-person contributions with praise and growth areas, helping individuals and leadership understand velocity and learning.
Trend tracking: maintains a history of metrics to surface improvements over sprints or weeks, enabling data-driven retrospectives.

Quick Start

Ask Claude to generate the weekly engineering retrospective for the current sprint.

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

To generate a weekly engineering retrospective, analyze commit history, work patterns, and code quality metrics to produce a concise report with per-person insights and trend analysis. This automatically surfaces contributions and growth areas across the team.

What is a team-aware retrospective and how does it track developer contributions?▼

A team-aware retrospective tracks developer contributions by analyzing commit history and code quality metrics to highlight individual praise and growth areas. It maintains persistent history to surface velocity and learning trend lines across sprints.

Can I track code quality metrics and work patterns over multiple sprints?▼

Yes, you can track code quality metrics and work patterns over multiple sprints by maintaining persistent history. This enables data-driven retrospectives by surfacing improvements and trend lines across weekly intervals.

Does the retrospective analysis work for engineering teams across different projects?▼

Yes, retrospective analysis applies to engineering teams across multiple projects. It aggregates work patterns and metrics into a unified report, ensuring team-wide insights and per-person contributions are captured regardless of project structure.

How do I surface per-person growth areas and praise in a data-driven retrospective?▼

Surface per-person growth areas and praise by analyzing individual commit history and code quality metrics. This identifies specific learning opportunities and achievements, providing actionable feedback within the weekly retrospective.

What's the best way to automate weekly sprint retrospectives without scattered notes?▼

Automate weekly sprint retrospectives by analyzing commit history and code quality metrics directly. This eliminates scattered notes by producing a persistent, team-aware report with actionable insights, per-person feedback, and trend tracking.