skills.rest
binfen1
binfen1COMMUNITY
Explore all skills by this author →
GitHub

retro

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

Updated Mar 23, 2026
Search Tags:#engineering#code-quality#commit-history#retro#team-performance#growth-feedback
One-click install
npx skills add https://github.com/binfen1/my-skills --skill retro-binfen1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/binfen1/my-skills/tree/main/claude-code/retro
Command: npx skills add https://github.com/binfen1/my-skills --skill retro-binfen1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives are often manual, inconsistent, and miss long-running trends. This Skill automatically analyzes commit history, work patterns, and code quality metrics to generate a structured, team-aware retrospective with persistent history.

Core Features & Use Cases

  • Per-person contribution breakdown with praise and growth areas.
  • Persistent historical trends across sprints and projects.
  • Proactive end-of-sprint prompts that surface improvements and action items.

Quick Start

Ask me to generate the weekly retro for this sprint by saying 'weekly retro'.

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

Generate a weekly engineering retrospective by analyzing commit history, work patterns, and code quality metrics. The system produces a structured, team-aware retrospective with per-person contributions, praise, growth areas, and persistent historical trends.

What is the best way to automate sprint retrospectives for code quality and team performance?▼

Automate sprint retrospectives by identifying team contributions and code quality signals across the latest sprint. This approach generates actionable recommendations and trend history, replacing manual inconsistent reviews with proactive end-of-sprint insights.

Does this retrospective tool provide per-person contribution breakdowns with feedback?▼

Yes, the retrospective tool provides a per-person contribution breakdown. It highlights individual praise and growth areas based on commit activity and code quality signals, delivering clear output suitable for engineering teams.

Can I track persistent historical trends across multiple sprints for engineering teams?▼

You can track persistent historical trends across sprints and projects. The retrospective system maintains history to surface long-running patterns, proactive insights, and actionable recommendations for continuous team performance improvement.

How do I start a weekly retro for my team?▼

Start a weekly retro by prompting the system to analyze the latest sprint. It identifies team contributions, commit activity, and code quality signals to produce a structured retrospective with actionable recommendations and trend history.

Related Skills

Explore More Software Engineering Skills→
256javy256javy

retro

Aggregate commit history and code quality metrics into weekly engineering retrospectives.

Community
Advanced
hilaryosbornehilaryosborne

tl-retro

Facilitate team retrospectives to identify SMART action items for process improvement.

Community
Intermediate
AlejandroFiginiAlejandroFigini

retro

Analyze commit history and code quality trends to generate weekly retrospective summaries.

Community
Intermediate
yocxy2yocxy2

retro

Analyze commit history and work patterns to generate engineering retrospective reports.

Community
Advanced