skills.rest
aicodepro
aicodeproOFFICIAL
Explore all skills by this author →
GitHub

retro

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

Updated Jun 22, 2026
Search Tags:#git#retrospective#engineering metrics#commit analysis#sprint review#gstack#team analytics
One-click install
npx skills add https://github.com/aicodepro/ai-agent-nexi --skill retro-aicodepro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/aicodepro/ai-agent-nexi/tree/main/agent/skills/gstack/retro
Command: npx skills add https://github.com/aicodepro/ai-agent-nexi --skill retro-aicodepro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering teams often lack visibility into what was actually shipped during a week or sprint, and writing retrospectives manually from scattered commit history is tedious and inconsistent. This Skill automates the analysis of commit history, work patterns, and code quality metrics to produce a structured weekly retrospective. ## Core Features & Use Cases - Commit and Work Pattern Analysis: Reviews git history and code quality metrics to summarize what the team shipped during the period. - Persistent Trend Tracking: Stores retrospective history so trends in output and quality can be compared across weeks. - Team-Aware Breakdowns: Splits contributions per person, highlighting praise-worthy work and growth areas for each team member. - Use Case: At the end of a sprint, ask for a weekly retro and receive a per-person summary of shipped work, quality trends versus prior weeks, and talking points for the team meeting. ## Quick Start Ask the assistant to run a weekly engineering retrospective analyzing what the team shipped this week.

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

Invoke the retro skill with a phrase like "weekly retro" or "what did we ship". It analyzes commit history, work patterns, and code quality metrics, then produces a structured retrospective with per-person breakdowns.

What does the retro skill analyze in a repository?▼

It analyzes commit history, work patterns, and code quality metrics for the current repository. Results include per-person contributions with praise and growth areas, plus trend comparisons against stored retrospective history.

Does the retrospective track trends over multiple weeks?▼

Yes, the skill keeps persistent history of past retrospectives and uses it for trend tracking. Each run can compare current output and quality metrics against previous weeks or sprints.

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

Yes, it is team-aware and breaks down shipped work per person. Each breakdown highlights praise-worthy contributions and identifies growth areas for individual team members.

When should I run an engineering retrospective?▼

Run it at the end of a work week or sprint, which is when the skill may also proactively suggest itself. It works best on repositories with regular commit activity so the analysis has meaningful history to review.

Related Skills

Explore More Software Engineering Skills→
26mitch2626mitch26

gstack-openclaw-retro

Analyze Git commit history to generate engineering retrospective reports.

Community
Advanced
pcaokhaipcaokhai

retro

Generate weekly engineering retrospectives from commit history and code quality metrics.

Community
Advanced
alexaundrealexaundre

retro

Generates engineering retrospective reports from git commit history and time-windowed analysis.

Community
Intermediate
baleen37baleen37
4

daily-standup

Aggregates Jira issues into formatted daily standup reports for the current user.

Community
Intermediate