skills.rest
tony30552001
tony30552001COMMUNITY
Explore all skills by this author →
GitHub

gstack-openclaw-retro

Generate weekly engineering retrospectives from Git commit history and team metrics.

Updated Dec 26, 2025
Search Tags:#git#metrics#engineering#growth#team#retro#praise
One-click install
npx skills add https://github.com/tony30552001/Genpic-master --skill gstack-openclaw-retro-tony30552001
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-openclaw-retro
Source: https://github.com/tony30552001/Genpic-master/tree/main/.agents/skills/gstack/openclaw/skills/gstack-openclaw-retro
Command: npx skills add https://github.com/tony30552001/Genpic-master --skill gstack-openclaw-retro-tony30552001

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives are time-consuming and prone to inconsistency. This skill automates analysis of commit history, team contributions, and code quality metrics to produce a structured retro with persistent history and growth-focused feedback.

Core Features & Use Cases

  • Analyzes commit history, work patterns, and code quality metrics.
  • Maintains persistent history and trend tracking per team member.
  • Generates team-wide praise and growth opportunities.
  • Use when asked for weekly retro, what shipped this week, or engineering retrospective.

Quick Start

Ask the retro tool to generate the weekly engineering retrospective for the last 7 days.

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 a weekly engineering retrospective from Git commit history?▼

Automate a weekly engineering retrospective by analyzing local Git commit history, performance metrics, and team contributions to generate a structured summary with per-person praise and growth notes.

Can I generate an engineering retro report for specific time windows like the last 24 hours or 30 days?▼

Yes, you can generate an engineering retro report for specific time windows including the last 24 hours, 7 days, 14 days, or 30 days, and use a compare mode to assess changes between periods.

Does the weekly retro tool track individual team member growth over time?▼

Yes, the weekly retro tool maintains persistent history and trend tracking per team member, generating team-wide praise and specific growth opportunities based on code quality metrics and work patterns.

How do I compare engineering metrics and team contributions between two different time periods?▼

Compare engineering metrics and team contributions between two different time periods using the built-in compare mode, which assesses changes in commit history and performance data across the selected windows.

Do I need to connect a remote repository to analyze code quality metrics for my team retro?▼

No, you do not need to connect a remote repository; the retro tool operates on local repository data and enforces local timezone reporting to ensure accurate commit history analysis.

What is the best way to prepare a narrative report of what shipped this week from local Git data?▼

Prepare a narrative report of what shipped this week by running the retro tool on local Git data, which outputs a structured summary of engineering contributions and code quality metrics suitable for dashboards.

Related Skills

Explore More Software Engineering Skills→
26mitch2626mitch26

gstack-openclaw-retro

Analyze Git commit history to generate engineering retrospective reports.

Community
Advanced
serejarisserejaris
215

cc-analytics

Analyze Claude Code history and Git data into weekly HTML reports.

Community
Intermediate
kk20300113-pngkk20300113-png

retro

Analyze git commit history to generate weekly engineering retrospective reports.

Community
Advanced
mgher668mgher668

retro

Analyze commit history and code quality metrics to generate weekly engineering retrospectives.

Community
Advanced