retro

Name: retro
Availability: InStock
Author: sanskarbasnet

Aggregate commit history, work patterns, and quality metrics into weekly retrospectives.

1|Updated May 4, 2026

Search Tags:#retrospective #engineering #code-quality #sprint #commit-history #retro #team-growth

Ready to run

npx skills add https://github.com/sanskarbasnet/fstack --skill retro-sanskarbasnet

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/sanskarbasnet/fstack/tree/main/retro
Command: npx skills add https://github.com/sanskarbasnet/fstack --skill retro-sanskarbasnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retros help engineering teams surface bottlenecks, align on outcomes, and celebrate contributions by analyzing commit history, work patterns, and code-quality metrics across time.

Core Features & Use Cases

Team-aware breakdown of per-person contributions with praise and growth areas.
Persistent history and trend tracking to surface improvements over multiple sprints.
Proactive retrospectives: suggest the right moments to review and reflect, reducing context loss.

Quick Start

Ask for a weekly retro by saying "weekly retro" and the skill will generate a team-facing retrospective with insights and growth actions.

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 retrospective by aggregating commit history, work patterns, and code-quality metrics to compile timelines, learnings, and actionable growth insights.

What is a team-aware retrospective and how does it track engineering growth?▼

A team-aware retrospective tracks engineering growth by providing persistent historical context and trend tracking to surface bottlenecks, align on outcomes, and highlight improvements across multiple sprints.

How do I analyze per-person code contributions for a sprint review?▼

Analyze per-person code contributions by compiling commit history and work patterns into a retrospective that highlights individual praise areas and growth opportunities, providing growth-oriented feedback.

Can I track engineering sprint trends and historical project health over time?▼

Track sprint trends and historical project health by maintaining persistent history across retrospectives, allowing you to surface improvements and analyze work patterns and code-quality metrics over multiple sprints.

How do I get actionable insights from what my engineering team shipped this week?▼

Get actionable insights from what your team shipped by triggering a weekly retro aggregation that compiles commit timelines and quality metrics into a team-facing retrospective with growth actions.

Does running a code-quality retrospective require any specific dependencies?▼

Running a code-quality retrospective requires no specific dependencies, allowing you to directly aggregate work patterns and commit history to produce a retrospective with actionable insights.