skills.rest
shogo-labs
shogo-labsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

retro

Generates weekly engineering retrospective reports from repository commit history and team data.

12|6|Updated Dec 2, 2025
Search Tags:#retrospective#engineering#growth#code-quality#commit-history#retro#team-velocity
One-click install
npx skills add https://github.com/shogo-labs/shogo-ai --skill retro-shogo-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/shogo-labs/shogo-ai/tree/main/packages/agent-runtime/templates/virtual-engineering-team/.shogo/skills/gstack-retro
Command: npx skills add https://github.com/shogo-labs/shogo-ai --skill retro-shogo-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinated weekly engineering retros are difficult to assemble from scattered signals (commits, issues, and feedback). This Skill automates generating a structured, team-aware retrospective that surfaces contributions, trends, and growth opportunities from your repository history and project data.

Core Features & Use Cases

  • Per-person contribution breakdown with growth areas, enabling targeted coaching and recognition.
  • Persistent history and trend tracking across sprints to reveal long-term improvements and recurring issues.
  • Generates ready-to-share retros for weekly cadence, post-release reviews, or sprint-end reflections.

Quick Start

Run the retro skill to generate a weekly engineering retrospective from your repository history.

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

You can automate weekly engineering retrospectives by analyzing commit history, code quality signals, and team contributions to output a structured report with per-person breakdowns and trend analysis.

What is an automated engineering retro and how does it analyze team velocity?▼

An automated engineering retro analyzes commit history and code quality signals to evaluate team velocity, surfacing per-person contributions and persistent trend tracking across sprints for targeted coaching.

Can I use commit history to get per-person contribution breakdowns for sprint-end reviews?▼

Yes, analyzing commit history and team contributions generates per-person breakdowns with growth areas, enabling targeted coaching and recognition for sprint-end reviews and post-release reflections.

How do I track engineering growth and recurring code quality issues across sprints?▼

Track engineering growth and code quality issues by maintaining persistent history and trend analysis across sprints, revealing long-term improvements and recurring issues from project data and repository history.

Does this approach to engineering retrospectives work for post-release reflections?▼

Yes, this approach applies to post-release reflections and ongoing project retros across teams, generating ready-to-share reports that highlight wins, areas for growth, and concrete next steps from repository data.

Related Skills

Explore More Software Engineering Skills→
AlejandroFiginiAlejandroFigini

retro

Analyze commit history and code quality trends to generate weekly retrospective summaries.

Community
Intermediate
brand6brand6

retrospective

Extract sprint data into a structured markdown retrospective with actionable improvements.

Community
Advanced
Chang-Shih-YungChang-Shih-Yung

gstack-openclaw-retro

Compile weekly engineering retrospectives from git commit history.

Community
Advanced
BradliebsBradliebs

retro

Analyze commit history and work patterns to generate weekly engineering retrospectives.

Community
Advanced