skills.rest
tsensei
tsenseiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

retro

Analyze commit history and contributor patterns to produce structured engineering retrospectives.

3|3|Updated Mar 26, 2026
Search Tags:#metrics#engineering#code-quality#software-engineering#commit-history#retro#team-insights
One-click install
npx skills add https://github.com/tsensei/ReelMistri --skill retro-tsensei
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/tsensei/ReelMistri/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/tsensei/ReelMistri --skill retro-tsensei

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill generates a comprehensive engineering retrospective by analyzing commit history, contributor patterns, and code quality metrics to surface actionable insights for improving team health and delivery.

Core Features & Use Cases

  • Team-aware retrospectives: identifies who ran the retro, praises strong contributions, and highlights growth areas per person.
  • End-to-end analysis: aggregates commit activity, hotspots, tests, and quality signals to tell a coherent story of a sprint or week.
  • Executive-level planning: outputs structured insights suitable for planning sessions, team dialogues, and leadership reviews.
  • Designed for senior engineers and leaders: delivers in-depth, actionable feedback with concrete examples and next steps.

Quick Start

Run /retro to generate a weekly engineering retrospective for the current repository.

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

You can generate an engineering retrospective by analyzing commit history, contributor patterns, and code quality metrics to produce a concise report with per-author metrics and hotspots.

What are code quality metrics and how are they used in team retrospectives?▼

Code quality metrics are aggregated signals from repository activity used in team retrospectives to surface actionable insights, identify hotspots, and highlight per-person growth areas for improving team health.

Can I run a cross-project retrospective across multiple repositories?▼

Yes, you can run a cross-project retrospective across multiple AI coding tools or repositories, aggregating contributor patterns and code quality metrics for a unified analysis of team delivery.

Does the retrospective analysis identify individual contributor patterns?▼

Yes, retrospective analysis identifies individual contributor patterns by parsing per-author metrics within a specified time-window, allowing the report to deliver per-person praise and highlight specific growth areas.

What is the best way to summarize commit activity for an executive review?▼

The best way to summarize commit activity for an executive review is to aggregate code quality metrics and contributor patterns into a structured report suitable for leadership planning sessions.

Do I need a specific time window to analyze code quality metrics?▼

You need a specific time window to analyze code quality metrics, as the retrospective applies time-window parsing to accurately aggregate commit activity and contributor patterns for the report.

Related Skills

Explore More Software Engineering Skills→
YaugourtYaugourt
2

retro

Generate engineering retrospectives from commit history and contributor data over a specified window.

Community
Advanced
whd4whd4

retro

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

Community
Advanced
greencmgreencm
1

gstack-openclaw-retro

Automates engineering retrospectives by analyzing commit history, work patterns, and code quality metrics.

Community
Advanced
CarbeneAICarbeneAI
9

retro

Generate weekly engineering retrospectives from git logs and analytics files.

Community
Advanced