skills.rest
deflosj
deflosjOFFICIAL
Explore all skills by this author →
GitHub

gstack-openclaw-retro

Analyze Git history to generate weekly engineering retrospective metrics and summaries.

Updated Apr 20, 2026
Search Tags:#git#analysis#metrics#engineering#leadership#team#retro
One-click install
npx skills add https://github.com/deflosj/frontend --skill gstack-openclaw-retro-deflosj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-openclaw-retro
Source: https://github.com/deflosj/frontend/tree/main/.agents/skills/gstack/openclaw/skills/gstack-openclaw-retro
Command: npx skills add https://github.com/deflosj/frontend --skill gstack-openclaw-retro-deflosj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives traditionally require manual aggregation of commit history and team activity, slowing down feedback and growth. This Skill automates the collection and organization of code metrics, per-person contributions, praise, and growth opportunities, while maintaining a persistent history for trend analysis.

Core Features & Use Cases

  • Team-aware with per-person contributions, praise, and growth opportunities.
  • Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking.
  • Use when asked for weekly retro, what shipped this week, or engineering retrospective.

Quick Start

Ask it to generate a retro for the current window to see the latest metrics and narrative.

Frequently Asked Questions about gstack-openclaw-retro

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

FAQPage Schema
How do I automate weekly engineering retrospectives from Git history?▼

Automate weekly engineering retrospectives by analyzing Git history to produce comprehensive metrics, per-author summaries, and a narrative suitable for Telegram. This replaces manual aggregation of code activity for team feedback.

What engineering metrics can I track for a team retro?▼

Engineering retro metrics include commits, contributors, PRs, LOC, test ratio, a focus score, and a Ship of the Week. The analysis provides per-person contributions, praise, and growth opportunities.

Can I generate a Git analysis report for different time windows?▼

Git analysis supports multiple time windows for retrospectives. It applies to the current 7-day window by default and supports 24h, 14d, 30d, and compare options, returning local-time based metrics.

How do I track team growth and work patterns over time?▼

Track team growth and work patterns by analyzing commit history and code quality metrics with persistent history and trend tracking. This identifies per-person contributions, praise, and growth opportunities over time.

What is the best way to share code metrics and retro narratives with engineering leadership?▼

Share code metrics and retro narratives with engineering leadership by generating a Telegram-suitable narrative. This provides a comprehensive weekly retrospective including local-time based metrics and focus scores.

Do I need to manually configure dependencies to run an engineering retro?▼

No dependencies are required to run an engineering retro. The analysis operates independently to evaluate Git history and generate team-aware per-person contributions and code quality metrics.

Related Skills

Explore More Software Engineering Skills→
ligianehualigianehua

retro

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

Community
Advanced
JeremiahEllingtonJeremiahEllington

retro

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

Community
Advanced
NoobyGainsNoobyGains
78

quality-enforcement

Enforce code quality standards across pre-commit, pre-merge, and CI pipeline stages.

Community
Advanced
SoSoBurnerSoSoBurner

retro

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

Community
Advanced