skills.rest
westn
westnCOMMUNITY
Explore all skills by this author →
𝕏@westnGitHub

gstack-openclaw-retro

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

1|Updated Mar 15, 2026
Search Tags:#git#analytics#metrics#engineering#retro#team-analysis
One-click install
npx skills add https://github.com/westn/gstack-pi-port --skill gstack-openclaw-retro-westn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-openclaw-retro
Source: https://github.com/westn/gstack-pi-port/tree/main/port/gstack/openclaw/skills/gstack-openclaw-retro
Command: npx skills add https://github.com/westn/gstack-pi-port --skill gstack-openclaw-retro-westn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retros are essential to understand team performance, identify bottlenecks, and celebrate contributions. This Skill analyzes commit history, work patterns, and code quality metrics across a persistent history to produce actionable insights. It is team-aware, highlighting per-person contributions, praises, and growth areas to guide improvement.

Core Features & Use Cases

  • Team-wide retrospectives that summarize who shipped what, when, and how code quality evolved over time.
  • Per-person insights including praise and growth opportunities based on commit activity, hotspots, and session patterns.
  • Historical trend tracking with persistent memory to compare weeks and surface focus areas.

Quick Start

Run the retro generator to compile a weekly report from the repository’s git history and generate a narrative with metrics and recommendations.

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 retros by analyzing git history, team contributions, and code quality metrics to generate a narrative report with praises and growth areas. The Skill aggregates per-author commits and tracks persistent trends to summarize what shipped and what improved.

What metrics are included in a git-based team retrospective?▼

A git-based team retrospective includes per-author commit activity, hotspot analysis, session patterns, and ship metrics to highlight individual contributions. It tracks code quality evolution over time to identify bottlenecks and celebrate team performance.

Can I track historical engineering trends across multiple weekly retros?▼

Historical trend tracking uses persistent memory to compare weekly engineering retros and surface focus areas across sessions. This allows teams to monitor code quality evolution and work patterns over time rather than just analyzing a single week.

Does generating an engineering retro require any external analytics dependencies?▼

Generating an engineering retro requires no external dependencies, operating directly on git logs to collect data. It performs per-author aggregation and hotspot analysis internally to produce the narrative output.

What is the best way to analyze code quality and team contributions for a retro?▼

The best way to analyze code quality for a retro is using a tool that aggregates git logs and tracks persistent history to produce actionable insights. This approach identifies bottlenecks and celebrates contributions through a narrative format rather than manual review.

Related Skills

Explore More Data & Analytics Skills→
ligianehualigianehua

retro

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

Community
Advanced
mahg-esmahg-es
3

velocity

Calculate team velocity metrics from sprint history and generate a velocity report.

Official
Intermediate
arisngarisng
5

commit-scope-constitution

Generates and updates commit scope inventories from git history and templates.

Community
Basic
fghaffarfghaffar

retro

Generate weekly engineering retrospective reports from Git commit history and metrics.

Community
Advanced