skills.rest
tblakex01
tblakex01COMMUNITY
Explore all skills by this author →
GitHub

gstack-openclaw-retro

Analyze commit history to generate structured weekly engineering retrospectives.

1|Updated Apr 26, 2026
Search Tags:#git#analytics#metrics#engineering#team#commit-history#retro
One-click install
npx skills add https://github.com/tblakex01/conductor-playground --skill gstack-openclaw-retro-tblakex01
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-openclaw-retro
Source: https://github.com/tblakex01/conductor-playground/tree/main/.claude/skills/gstack/openclaw/skills/gstack-openclaw-retro
Command: npx skills add https://github.com/tblakex01/conductor-playground --skill gstack-openclaw-retro-tblakex01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly post-mortems of engineering activity can be time-consuming and rely on scattered data. This Skill consolidates commit history, work patterns, and code quality metrics into a single retrospective.

Core Features & Use Cases

  • Generates team-aware retrospectives with per-person praise and growth areas.
  • Maintains persistent history and trend data for week-over-week comparisons.
  • Use when asked for weekly retro, what shipped this week, or a general engineering retrospective.

Quick Start

Generate the weekly engineering retro for the default 7-day window.

Frequently Asked Questions about gstack-openclaw-retro

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

FAQPage Schema
How do I generate a weekly engineering retrospective from git commit history?▼

A team-aware engineering retrospective summarizes weekly git commit activity by analyzing per-author metrics and code quality. It consolidates scattered data to highlight what shipped, work patterns, and individual growth areas for the team.

Can I track per-author metrics and work patterns for my engineering team?▼

Yes, you can track per-author metrics by parsing individual commit history and engineering activity. This process identifies specific work patterns, highlights what shipped per person, and generates praise and growth areas for team members.

How do I compare week-over-week engineering activity and code metrics?▼

You can compare week-over-week engineering activity by maintaining persistent history and trend data from your repository analytics. This allows you to parse sequential time-windows and track changes in commit volume and code quality metrics across retrospectives.

Does this weekly retro tool support Telegram-ready narrative output?▼

Yes, the weekly retro tool supports Telegram-ready narrative output directly. It formats the structured engineering activity summary, code quality metrics, and team retrospective insights into a narrative suitable for immediate messaging.

What is the best way to summarize what shipped this week across repositories?▼

The best way to summarize what shipped this week across repositories is to consolidate commit history and engineering activity into a single retrospective. This approach parses a default 7-day time window to produce structured metrics and team-aware insights.

Related Skills

Explore More Software Engineering Skills→
ShmurdocShmurdoc

gstack-openclaw-retro

Automate weekly engineering retros from git commit history.

Community
Advanced
algorithmbasicsalgorithmbasics

gstack-openclaw-retro

Analyze git history to generate weekly engineering retrospectives with per-author insights.

Community
Advanced
haJ1thaJ1t

auto-changelog

Generate CHANGELOG.md from git commit history using Conventional Commits.

Community
Advanced
BaGyun0107BaGyun0107

retro

Analyze commit history and work patterns for engineering retrospectives.

Community
Intermediate