skills.rest
manusco
manuscoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

retro

Generates git-driven retrospectives with shipping streak, focus score, and complexity delta.

Updated Dec 1, 2025
Search Tags:#git#retrospective#sprint review#developer metrics#focus score#shipping streak#complexity delta
One-click install
npx skills add https://github.com/manusco/wolfgang --skill retro-manusco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/manusco/wolfgang/tree/main/.cursor/skills/retro
Command: npx skills add https://github.com/manusco/wolfgang --skill retro-manusco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams and solo developers often lack a quick, data-backed way to review recent work. This Skill turns git history into a structured retrospective, removing the guesswork from reflecting on shipping cadence, focus, and code complexity trends. ## Core Features & Use Cases - Git-Driven Retrospective: Analyzes repository activity to produce a retrospective report. - Shipping Streak Tracking: Surfaces consecutive shipping activity as a streak metric. - Focus Score & Complexity Delta: Quantifies how focused recent work was and how code complexity changed. - Use Case: At the end of a sprint, run the /retro command to get an instant summary of your shipping streak, focus score, and complexity delta to discuss in your team review. ## Quick Start Ask the AI to run the retro command to generate a retrospective of recent git activity with shipping streak, focus score, and complexity delta.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I run a git-based retrospective on my project?▼

Invoke the /retro command in your AI assistant. It reads the retro procedure from the ops skill directory and analyzes your git history to produce a retrospective with shipping streak, focus score, and complexity delta.

What metrics does a git retrospective report include?▼

This retrospective includes three metrics: shipping streak (consecutive shipping activity), focus score (how concentrated recent work was), and complexity delta (how code complexity changed over the period).

Does the retro command require a git repository?▼

Yes, the retrospective is git-driven, so it analyzes repository commit history to compute its metrics. It should be run from within a project that uses git for version control.

Why does the retro command reference another SKILL.md file?▼

This skill is a thin router: it forwards the /retro command to the full procedure defined in .agents/skills/ops/retro/SKILL.md. That file contains the actual steps and Definition of Done that get executed.

When should I use a git retrospective versus manual sprint review?▼

Use the git retrospective when you want objective, commit-derived metrics quickly. For qualitative topics like team dynamics or blockers not visible in commits, a manual discussion is still needed.

Related Skills

Explore More Software Engineering Skills→
Jia-Hong-PengJia-Hong-Peng

retro

Analyze git commit history to generate weekly engineering retrospectives.

Community
Advanced
cegit27cegit27
3

retro

Analyze git commit history to generate weekly retrospective reports.

Official
Advanced
esopianesopian
2

retro

Analyze git commit history and code metrics to generate team retrospectives.

Community
Intermediate
emcconnellemcconnell

retrospective

Generate structured Markdown retrospectives from sprint plans and git commit history.

Community
Advanced