skills.rest
BasharAmso
BasharAmsoCOMMUNITY
Explore all skills by this author →
GitHub

Team Retro

Generates data-driven engineering retrospectives from Git commit history, TODOS, and DECISIONS.

1|Updated Mar 11, 2026
Search Tags:#git#metrics#retrospective#engineering#velocity#contributors
One-click install
npx skills add https://github.com/BasharAmso/Bashi --skill team-retro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Team Retro
Source: https://github.com/BasharAmso/Bashi/tree/main/create-bashi-app/template/.claude/skills/retro
Command: npx skills add https://github.com/BasharAmso/Bashi --skill team-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineering retrospectives are often manual, scattered, and hard to track across teams. This skill automates the analysis of commit history, per-contributor performance, and project decisions to reveal actionable insights that guide improvement.

Core Features & Use Cases

  • Per-contributor analysis with praise and growth suggestions
  • Streak tracking, focus scores, and trend comparisons
  • Configurable time windows (24h, 7d, 14d, 30d) and cross-project summaries
  • Generate narrative retrospectives and JSON snapshots for trend tracking

Quick Start

Request a Team Retro for the most recent sprint to generate a narrative, metrics snapshot, and updated state

Frequently Asked Questions about Team Retro

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

FAQPage Schema
How do I generate a data-driven engineering retrospective from Git commit history?▼

Generate a data-driven engineering retrospective by analyzing Git commit history, TODOS.md, and DECISIONS files to surface focus, streaks, trends, and growth opportunities. This produces a narrative output, a JSON snapshot, and an updated STATE.md.

Can I analyze per-contributor performance and velocity for a specific time window?▼

Yes, you can analyze per-contributor performance and velocity using configurable time windows of 24 hours, 7 days, 14 days, or 30 days to surface focus scores, streak tracking, and trend comparisons.

What is a data-driven team retrospective and how does it track engineering metrics?▼

A data-driven team retrospective automates the analysis of commit history and project decisions to track engineering metrics like velocity and focus. It replaces manual, scattered tracking with actionable insights for improvement.

Does this approach require any external dependencies to parse Git metrics?▼

No, this approach requires no external dependencies to parse Git metrics. It runs entirely within your environment to analyze commit history and generate retrospective snapshots locally.

How do I track engineering retrospective trends and state over time?▼

Track engineering retrospective trends over time by generating JSON snapshots saved under .claude/project/retros and an updated STATE.md file. These outputs allow you to monitor per-contributor growth and cross-project summaries historically.

Related Skills

Explore More Software Engineering Skills→
jkhowlandjkhowland

retro

Analyze Git repository history to generate engineering retrospectives for defined time windows.

Community
Advanced
asapMakiasapMaki

sedmicni-summary

Aggregate daily summaries into a structured weekly markdown report.

Community
Basic
kmshihab7878kmshihab7878
6

Scrum Master

Break epics into user stories and plan sprint iterations with velocity metrics.

Community
Advanced
shekerkammashekerkamma

gstack-openclaw-retro

Automates weekly engineering retrospective metrics from git commit history with configurable windows and saved snapshots.

Community
Advanced