skills.rest
geoffreywoo
geoffreywooCOMMUNITY
Explore all skills by this author →
Website𝕏@geoffreywooGitHub

retro

Generates weekly engineering retrospective reports from Git commit history and per-author statistics.

1|Updated Feb 27, 2026
Search Tags:#analytics#retrospective#growth#commit-history#retro#team-praise
One-click install
npx skills add https://github.com/geoffreywoo/clawfable --skill retro-geoffreywoo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/geoffreywoo/clawfable/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/geoffreywoo/clawfable --skill retro-geoffreywoo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often lack a structured, data-driven way to review weekly work, celebrate contributions, and identify growth areas. This skill aggregates commit history, per-person activity, and code-quality signals to produce a team-aware retrospective that persists across sprints.

Core Features & Use Cases

  • Per-person praise and growth opportunities based on contribution data
  • Persistent history of retros with trend tracking across weeks
  • Per-project and per-branch insights for actionable improvements
  • Generates clear, shareable summaries for team meetings and one-on-ones

Quick Start

Invoke /retro to generate the current week's retrospective.

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, per-author contributions, and code quality metrics to produce a structured team performance review with praise and growth areas.

What is a data-driven engineering retro and how does it track team growth?▼

A data-driven engineering retro aggregates per-author contribution data and code quality signals to capture team praise, identify growth opportunities, and track performance trends persistently across sprints.

Can I analyze per-person code contributions and branch insights for sprint reviews?▼

Yes, you can analyze per-person code contributions and per-branch insights to generate shareable sprint review summaries that highlight individual performance and actionable project improvements.

How do I track engineering topic trends and per-author performance across multiple sprints?▼

Track engineering trends and per-author performance across sprints by maintaining a persistent history of retrospectives, aggregating weekly contribution data to visualize growth and topic progression over time.

Does this retrospective tool work without external dependencies or integrations?▼

Yes, the retrospective skill operates independently without external dependencies, parsing Git data internally to aggregate stats and present an actionable plan for the next development cycle.

What is the best way to prepare actionable plans for the next sprint cycle based on Git data?▼

Prepare actionable plans by parsing Git data to aggregate per-author statistics and code quality metrics, generating a retrospective that identifies specific growth areas and topics for the next cycle.

Related Skills

Explore More Software Engineering Skills→
cegit27cegit27
3

retro

Analyze git commit history to generate weekly retrospective reports.

Official
Advanced
antriksh-29antriksh-29

retro

Analyze git history to generate team retrospectives with per-person metrics and trends.

Community
Advanced
az9713az9713
2

retro

Generate weekly engineering retrospective reports from commit history and code quality metrics.

Community
Intermediate
SeongHuniSeongHuni

retrospective

Generate sprint or milestone retrospectives by analyzing project data.

Community
Intermediate