skills.rest
scanbott
scanbottCOMMUNITY
Explore all skills by this author →
GitHub

retro

Analyze commit history and work patterns to summarize weekly engineering performance.

Updated Apr 21, 2026
Search Tags:#engineering#growth#code-quality#sprint#retro#team-feedback
One-click install
npx skills add https://github.com/scanbott/claude-skills --skill retro-scanbott
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/scanbott/claude-skills/tree/main/gstack/retro
Command: npx skills add https://github.com/scanbott/claude-skills --skill retro-scanbott

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospective that analyzes commit history, work patterns, and code quality metrics to surface trends, praise, and growth opportunities with persistent context.

Core Features & Use Cases

  • Analyze commit histories and work patterns across sprints to surface actionable insights.
  • Break down contributions per team member and identify praise and growth areas.
  • Maintain a persistent session history to track improvements over time and inform planning.

Quick Start

Request a weekly retro for the current sprint by saying "weekly retro" in the chat.

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

Generate a weekly retro by requesting it in chat during sprint end. It analyzes your commit history, work patterns, and code quality metrics to output a structured performance briefing.

What is a sprint retrospective analysis and how does it track team growth?▼

Sprint retrospective analysis evaluates engineering performance to identify praise and growth areas. It maintains persistent session history to track team improvements and surface actionable trends over time.

Can I get per-person code quality metrics and contributions for my team?▼

Yes, you can get per-person contributions. The analysis breaks down individual work patterns and code quality metrics to highlight specific team member contributions and areas for growth.

What's the best way to summarize weekly engineering performance for team reviews?▼

The best way to summarize weekly engineering performance is applying this analysis at sprint end. It surfaces actionable insights and outputs a structured briefing specifically designed for team reviews.

Does the weekly retro require any specific integrations to analyze work patterns?▼

No specific integrations are required. The retro operates without dependencies to analyze commit histories and work patterns, relying on your existing engineering data.

When should I run a sprint retro to get the most accurate performance insights?▼

You should run a sprint retro at the end of your sprint. Applying the analysis then ensures it captures the complete commit history and code quality metrics for that cycle.

Related Skills

Explore More Software Engineering Skills→
256javy256javy

retro

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

Community
Advanced
mahg-esmahg-es
3

retrospective

Facilitate structured sprint retrospectives and generate action plans.

Official
Intermediate
OpenAnalystIncOpenAnalystInc
3

10x-team

Coordinates team rituals and manages workflows through customizable, automated processes in Notion.

Official
Advanced
mgher668mgher668

retro

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

Community
Advanced