skills.rest
ComputerConnection
ComputerConnectionCOMMUNITY
Explore all skills by this author →
GitHub

retro

Analyze weekly git activity to generate team-aware retrospectives with per-author metrics.

Updated Mar 31, 2026
Search Tags:#git#analytics#metrics#code-quality#sprint#team#retro
One-click install
npx skills add https://github.com/ComputerConnection/zach-pack --skill retro-computerconnection
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/ComputerConnection/zach-pack/tree/main/skills/gstack-retro
Command: npx skills add https://github.com/ComputerConnection/zach-pack --skill retro-computerconnection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives that analyze commit history, work patterns, and code quality with persistent history and growth-oriented praise.

Core Features & Use Cases

  • Team-aware per-person praise and growth opportunities
  • Persistent history and trend tracking across sprints
  • Auto-generated narratives for CTO-level reviews and leadership updates

Quick Start

Invoke /retro to generate the latest weekly retrospective for the default 7-day window.

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

To generate a weekly engineering retrospective from git history, invoke the /retro command to analyze the default 7-day commit window. This automatically produces per-author praise, growth areas, and narrative-ready summaries for your sprint.

Can I track code quality and contributor metrics across multiple sprints?▼

Yes, you can track code quality and contributor metrics across multiple sprints because the retrospective maintains persistent history. This allows you to perform trend analysis and compare per-author metrics and hotspot patterns over time.

What is included in a git-based team retrospective for leadership reviews?▼

A git-based team retrospective for leadership reviews includes auto-generated narratives highlighting individual contributions, work patterns, and growth opportunities. It provides a comprehensive summary of engineering activity suitable for CTO-level updates.

Does the sprint retrospective analysis support exporting team metrics?▼

Yes, sprint retrospective analysis supports exporting team metrics by generating an exportable JSON snapshot. This snapshot captures retros history, per-author metrics, and trend analyses for external reporting or archival purposes.

Do I need any specific dependencies to run git analytics for team retrospectives?▼

No specific dependencies are required to run git analytics for team retrospectives. The tool works with git-based projects across all contributors without needing additional components or environment setup to analyze your engineering activity.

Related Skills

Explore More Software Engineering Skills→
abhishekmmgnabhishekmmgn

retro

Generate structured weekly retrospective narratives from git history, timelines, and learnings.

Community
Advanced
jpoleyjpoley
50

security-reporter

Consolidates vulnerability findings into audit reports with risk assessment and compliance mapping.

Community
Advanced
xuithoixuithoi

retro

Generates weekly engineering retrospectives from Git commit history and code metrics.

Community
Advanced
him55710-sudohim55710-sudo

retro

Analyze commit history and contributor activity to generate engineering retrospectives.

Community
Advanced