skills.rest
cheng80
cheng80COMMUNITY
Explore all skills by this author →
GitHub

retro

Analyze commit history and work patterns for weekly engineering retrospectives.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospective analytics that analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking, providing team-aware insights and growth feedback.

Core Features & Use Cases

  • Analyze commit history and team work patterns to surface actionable insights.
  • Track code quality metrics over time with per-person contribution breakdowns.
  • Proactively suggest improvements at the end of a sprint or work week.

Quick Start

Ask for a weekly retro and I will analyze the latest commits, trends, and team contributions.

Frequently Asked Questions about retro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze commit history for a weekly engineering retrospective?▼

Analyzing commit history for a weekly engineering retrospective involves inspecting work patterns and team contributions to surface actionable insights. This process tracks code quality metrics and provides growth recommendations for sprint-end reviews.

What is the best way to track team health signals and per-person contributions?▼

Tracking team health signals and per-person contributions requires analyzing weekly engineering activity to evaluate work patterns. This approach provides persistent historical trends and team-aware insights to measure overall team growth.

Can I get proactive improvement suggestions at the end of a sprint?▼

Yes, you can get proactive improvement suggestions at the end of a sprint by analyzing weekly engineering activity. This surfaces actionable code quality insights and growth recommendations based on recent commit history.

Does the weekly retro process support persistent historical trends and code quality metrics?▼

The weekly retro process supports persistent historical trends by tracking code quality metrics over time. It provides per-person contribution breakdowns and maintains team-aware insights for continuous engineering growth.

How do I generate ship metrics for a sprint-end review?▼

Generating ship metrics for a sprint-end review involves analyzing weekly engineering activity and commit history. This surfaces team-health signals and actionable insights to evaluate code quality and per-person contributions.

Related Skills

Explore More Software Engineering Skills→
alangebalangeb

git-advanced

Perform Git bisecting, cherry-picking, and log analysis operations locally.

Community
Advanced
scanbottscanbott

retro

Analyze commit history and work patterns to summarize weekly engineering performance.

Community
Advanced
VanLVanL
1

gstack-openclaw-retro

Analyze Git commit history to generate engineering retrospectives with team activity and code quality metrics.

Community
Advanced
BradliebsBradliebs

retro

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

Community
Advanced