skills.rest
Scivor
ScivorCOMMUNITY
Explore all skills by this author →
Website𝕏@Scivor_AIGitHub

retro

Analyze commit history to generate per-person retrospective narratives.

Updated Apr 11, 2026
Search Tags:#git#metrics#engineering#code-quality#retro#team-performance
One-click install
npx skills add https://github.com/Scivor/helm --skill retro-scivor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/Scivor/helm/tree/main/skills/gstack/retro
Command: npx skills add https://github.com/Scivor/helm --skill retro-scivor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives that surface actionable insights from what happened in the last cycle.

Core Features & Use Cases

  • Per-person contributions: identify who did what and how it affected the sprint.
  • Metrics-driven review: analyzes commit history, code quality signals, and workflow latency.
  • Growth-oriented feedback: highlights praise and areas for improvement to guide next steps.

Quick Start

Ask me to run the retro workflow by saying 'retro' or 'weekly retro' and I will analyze commits, contributions, and code-quality signals to produce a team-ready retrospective.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate engineering retrospectives from git commit history?▼

Engineering retrospectives from git commit history are generated by parsing commits to extract per-user contributions and compute metrics like commit volume, churn, and review latency into a structured narrative.

Can I measure team performance using code quality signals and commit metrics?▼

You can measure team performance by analyzing commit history alongside code quality signals and workflow latency to surface per-person contributions and growth opportunities for weekly sprints.

What is the best way to analyze per-person contributions in a weekly sprint?▼

Analyzing per-person contributions in a weekly sprint is best done by parsing commit history and computing metrics like commit volume, code churn, and review latency to identify individual impacts.

How do I calculate code churn and review latency for growth-oriented feedback?▼

Calculating code churn and review latency for growth-oriented feedback involves parsing commit history to extract contributions, producing a structured retrospective that highlights praise and areas for improvement.

Does this retrospective workflow work without external dependencies?▼

This retrospective workflow operates without external dependencies, autonomously parsing engineering work history to surface actionable insights and growth opportunities from your ongoing projects.

Related Skills

Explore More Software Engineering Skills→
ligianehualigianehua

retro

Analyze git commit history to generate a team-aware weekly retrospective.

Community
Advanced
BatsiraiBatsirai

retro

Analyze Git commit history and code quality metrics to generate team-aware retrospective narratives.

Community
Advanced
cloudofgeorgecloudofgeorge

retro

Summarize git commit history and quality signals into structured retrospectives.

Community
Advanced
bitwardenbitwarden
129

retrospecting

Generate structured retrospective reports from Claude Code session data.

Official
Intermediate