skills.rest
tyhuffman7
tyhuffman7COMMUNITY
Explore all skills by this author →
GitHub

retro

Generate weekly engineering retrospectives from commit history and code quality metrics.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives that analyze commit history, work patterns, and code quality metrics to surface praise, growth areas, and actionable improvements with persistent history.

Core Features & Use Cases

  • Per-person contributions breakdown with context and growth suggestions.
  • Trend tracking over multiple sprints to expose patterns in delivery and quality.
  • Proactive end-of-week prompts to plan improvements and celebrate wins.
  • Use cases: "weekly retro," "what did we ship," or "engineering retrospective" to reflect and plan.

Quick Start

Run the retro skill at the end of a sprint to generate the team retrospective from repository history and metrics.

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 repository commit history, work patterns, and code quality metrics to surface praise, growth areas, and actionable improvements with persistent history.

How does trend analysis over multiple sprints work for code quality metrics?▼

Trend analysis tracks code quality metrics and delivery patterns over multiple sprints by storing retrospective results persistently, exposing team growth trends and historical performance breakdowns.

Can I get per-person contribution breakdowns from repository data for team retros?▼

Yes, per-person contribution breakdowns are generated from repository and attribution data, providing individual context, growth suggestions, and delivery insights for team-wide projects.

What is the best way to automate end-of-week sprint retrospectives with proactive suggestions?▼

Automate end-of-week sprint retrospectives by reading repository data and quality signals to deliver proactive prompts, celebrating wins and planning actionable improvements for the next sprint.

Do I need external dependencies to run engineering retrospectives on repository data?▼

No external dependencies are required to run engineering retrospectives; the skill reads repository data, attribution data, and quality signals directly to generate insights and store results.

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
BradliebsBradliebs

retro

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

Community
Advanced
koderoverkoderover
7

sonar

Retrieve and analyze SonarQube code quality metrics and quality gate statuses.

Official
Intermediate
256javy256javy

retro

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

Community
Advanced