skills.rest
adamtpang
adamtpangCOMMUNITY
Explore all skills by this author →
Website𝕏@adamtpangGitHub

retro

Analyzes commit history and work patterns to generate weekly engineering retrospectives with trend tracking.

Updated Jun 16, 2026
Search Tags:#git#retrospective#commit analysis#sprint review#team metrics#gstack#trend tracking
One-click install
npx skills add https://github.com/adamtpang/summon.company --skill retro-adamtpang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/adamtpang/summon.company/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/adamtpang/summon.company --skill retro-adamtpang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running a meaningful weekly engineering retrospective requires manually digging through commit history, recalling what shipped, and tracking team contributions over time. This Skill automates that analysis and keeps a persistent history so trends are visible across weeks. ## Core Features & Use Cases - Commit and work-pattern analysis: Reviews commit history, code quality metrics, and work patterns to summarize what the team shipped. - Team-aware breakdowns: Breaks down per-person contributions with praise and growth areas for each team member. - Persistent history and trends: Stores prior retros, timeline events, and learnings under ~/.gstack/projects/ so each retro builds on previous ones. - Use Case: At the end of a sprint, ask "what did we ship this week" and receive a structured retrospective covering shipped work, per-person contributions, and trends versus prior weeks. ## Quick Start Ask the assistant to run the weekly retro to analyze this week's commits and generate an engineering retrospective.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I run a weekly engineering retrospective with AI?▼

Invoke the retro skill with a phrase like "weekly retro" or "what did we ship". It analyzes commit history and work patterns, then produces a retrospective with per-person contributions, praise, and growth areas.

How does the retro skill track trends over time?▼

It stores prior retros as markdown files plus timeline and learnings JSONL logs under ~/.gstack/projects/<repo>/. Each run loads the five most recent retros and recent timeline events so new retrospectives can compare against previous weeks.

Does the retro skill break down contributions per team member?▼

Yes. The skill is team-aware and breaks down per-person contributions from commit history, highlighting praise and growth areas for each contributor in the retrospective output.

Can the retro skill run in headless or spawned agent sessions?▼

Yes. The preamble detects session kind (interactive, headless, or spawned) and adapts: spawned sessions skip interactive prompts and auto-choose recommended options, while headless sessions block instead of prompting.

What are the limitations of automated commit-based retrospectives?▼

The analysis is grounded in commit history and recorded timeline events, so work not captured in commits or logs (meetings, design discussions, reviews) may be underrepresented. It works best in repositories with consistent commit hygiene.

Related Skills

Explore More Software Engineering Skills→
abdulazeezojabdulazeezoj

retro

Analyzes commit history and code metrics to generate weekly engineering retrospectives.

Community
Advanced
autostay-krautostay-kr
1

retro

Facilitate structured sprint retrospectives and generate prioritized action plans.

Official
Intermediate
yashs33244yashs33244
1

retro

Generate weekly engineering retrospectives from commit history and work patterns.

Community
Advanced
monang404monang404
2

team-collaboration-standup-notes

Generates daily standup notes from Git commits, Jira tickets, and Obsidian vault data.

Community
Intermediate