skills.rest
Jesse-L-M
Jesse-L-MCOMMUNITY
Explore all skills by this author →
GitHub

retro

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

Updated Mar 27, 2026
Search Tags:#metrics#engineering#code-quality#commit-history#retro#team-feedback
One-click install
npx skills add https://github.com/Jesse-L-M/scz-target-engine --skill retro-jesse-l-m
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/Jesse-L-M/scz-target-engine/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/Jesse-L-M/scz-target-engine --skill retro-jesse-l-m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically surfaces actionable insights from your team's software activity, turning raw commit data and quality signals into a clear weekly retrospective.

Core Features & Use Cases

  • Per-author praise and growth suggestions based on commit history and contributions.
  • Comprehensive metrics on code quality, test health, and activity patterns, with a leader board.
  • Production-ready narrative reports that help teams reflect and plan improvements.

Quick Start

Run /retro to generate your weekly engineering retrospective for the last 7 days.

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, contributor activity, and code quality metrics. Run /retro to automatically produce a comprehensive narrative report covering the last 7 days.

Can I get per-author feedback and growth suggestions based on code commits?▼

Yes, per-author feedback is generated by analyzing individual contributor activity and commit history. The retrospective provides tailored praise and growth suggestions for each team member based on their contributions.

What code quality and test health metrics are included in a sprint retrospective?▼

Sprint retrospective metrics include aggregated commits, insertions, deletions, and test health signals. These code quality metrics combine to deliver actionable outcomes and a contributor leaderboard.

Does the retrospective analysis support time windows beyond the default 7 days?▼

Yes, the retrospective analysis supports broader time windows beyond the default 7 days. You can adjust the reporting window to capture longer periods of commit history and contributor activity.

What is the best way to surface actionable insights from team code activity?▼

The best way to surface actionable insights from team code activity is to aggregate commit data and quality signals into a production-ready narrative report. This helps software teams reflect and plan improvements.

Related Skills

Explore More Software Engineering Skills→
bswrundquistbswrundquist

git-analyze

Analyze git repository history for activity, initiatives, bugs, and contributors.

Community
Advanced
Wilder1222Wilder1222
2

self-improvement

Evaluates sprint outcomes and generates improvement reports in docs/superomni/improvements/ for software teams.

Community
Advanced
alexmaruccialexmarucci

cicd

Monitor CI/CD pipeline metrics, tests, and deployment gates via Datadog.

Community
Advanced
abzhawabzhaw

data-visualization

Render real-time charts of agent activity and data trends on Julia's dashboard.

Community
Intermediate