skills.rest
algorithmbasics
algorithmbasicsCOMMUNITY
Explore all skills by this author →
𝕏@AlgorithmLlcGitHub

retro

Analyze commit history and code quality metrics to produce weekly engineering retrospective reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives that surface patterns in contributions, highlight praise, and identify growth areas to help teams improve over time.

Core Features & Use Cases

  • Team-aware analysis that attributes contributions per person with praise and growth suggestions.
  • Persistent history and trend tracking across weeks and sprints.
  • Proactive recommendations for what to improve next, including suggested follow-up actions.

Quick Start

Type /retro to generate a weekly retrospective for your current project.

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?▼

To generate a weekly engineering retrospective, you can use this Skill to analyze your repository's commit history and code quality metrics, producing a structured report with per-person praise and actionable growth opportunities.

Can I compare code quality metrics across different sprint periods?▼

Yes, this retrospective tool supports comparing periods, allowing you to track persistent history and analyze team work patterns, code quality metrics, and growth trends across different weeks or sprints.

Does the retrospective analysis work across multiple projects or just a single repository?▼

The retrospective analysis operates across both single-project and cross-project scopes, attributing contributions per person while analyzing work patterns and code quality metrics to provide comprehensive team growth insights.

What do I need to set up before running an automated engineering retro?▼

You need to provide access to your repository data so the system can analyze commit history, work patterns, and code quality metrics to output a structured retrospective report with proactive recommendations.

How does an automated code quality retrospective identify team growth opportunities?▼

An automated code quality retrospective identifies growth opportunities by analyzing commit history and work patterns to attribute contributions per person, highlighting specific praise and suggesting proactive follow-up actions for improvement.

Are there limitations to using automated retrospectives for software engineering teams?▼

This retrospective tool is specifically designed for software teams and requires repository data access; it operates on defined windows like the last 7 days and outputs structured insights rather than fixing code quality issues directly.

Related Skills

Explore More Software Engineering Skills→
thanh-abaiithanh-abaii
34

gs:retro

Analyze commit history and code quality metrics to create engineering retrospective reports.

Community
Advanced
serejarisserejaris
215

cc-analytics

Analyze Claude Code history and Git data into weekly HTML reports.

Community
Intermediate
JeremiahEllingtonJeremiahEllington

retro

Analyze git commit history and work patterns to generate team-wide retrospectives with per-person insights.

Community
Advanced
rmarino550rmarino550

retro

Generate engineering retrospective reports from commit history and code quality metrics.

Community
Advanced