skills.rest
nhattran998
nhattran998COMMUNITY
Explore all skills by this author →
WebsiteGitHub

retro

Analyze commit history and code quality metrics into weekly team retrospectives.

Updated Mar 30, 2026
Search Tags:#retrospective#engineering#growth#team#commit-history#retro
One-click install
npx skills add https://github.com/nhattran998/personal-athlete-agent --skill retro-nhattran998
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/nhattran998/personal-athlete-agent/tree/main/.agents/skills/gstack-retro
Command: npx skills add https://github.com/nhattran998/personal-athlete-agent --skill retro-nhattran998

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives summarize commit history, work patterns, and code quality metrics with persistent history and trend tracking. It also breaks down per-person contributions with praise and growth areas, helping teams improve collectively over time.

Core Features & Use Cases

  • Weekly retrospective workflow that compiles commit history, work patterns, and quality metrics into a coherent team narrative.
  • Persistent history and trend tracking to surface improvements and recurring issues over multiple sprints.
  • Team-aware insights that highlight individual contributions, praise, and growth opportunities.

Quick Start

Run the retro skill at the end of a sprint to generate a team-focused retrospective with actionable recommendations.

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 commit history, work patterns, and code quality metrics. The skill compiles these data points into a coherent team narrative with actionable recommendations at the end of a sprint.

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

A team-aware retrospective breaks down per-person contributions, highlighting individual praise and growth areas. It uses persistent history and trend tracking to surface improvements and recurring issues across multiple sprints.

Can I use commit history and code quality metrics for sprint retrospectives across different branches?▼

Yes, you can apply this retrospective workflow across sprints and branches. It analyzes commit history and code quality metrics to produce a historical trend view that supports decision-making for team leads.

What's the best way to track recurring engineering issues and team improvements over time?▼

Track recurring issues and team improvements by maintaining a persistent history of weekly retrospectives. This approach analyzes work patterns and code quality metrics to reveal team growth and actionable improvement areas over multiple sprints.

Does the retrospective workflow integrate with the gstack workflow environment?▼

Yes, the retrospective workflow integrates with the gstack workflow. It compiles work patterns and code quality metrics into a historical trend view that supports decision-making for team leads within that environment.

Related Skills

Explore More Software Engineering Skills→
ligianehualigianehua

retro

Analyze git commit history to generate a team-aware weekly retrospective.

Community
Advanced
ClyptAIClyptAI

retro

Analyze commit history and code quality to generate team-aware retrospective summaries.

Official
Advanced
bajajvinamrbajajvinamr

retro

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

Community
Advanced
yocxy2yocxy2

retro

Analyze commit history and work patterns to generate engineering retrospective reports.

Community
Advanced