skills.rest
chriswestt
chriswesttCOMMUNITY
Explore all skills by this author →
GitHub

gstack-openclaw-retro

Aggregate commit history and code quality signals into team retrospectives.

Updated Apr 21, 2026
Search Tags:#git#metrics#retrospective#engineering#code-quality#team-maintenance
One-click install
npx skills add https://github.com/chriswestt/claude-skills --skill gstack-openclaw-retro-chriswestt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-openclaw-retro
Source: https://github.com/chriswestt/claude-skills/tree/main/gstack/openclaw/skills/gstack-openclaw-retro
Command: npx skills add https://github.com/chriswestt/claude-skills --skill gstack-openclaw-retro-chriswestt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives can be time-consuming to assemble manually, often missing per-person context and actionable growth areas. This Skill automates the collection and synthesis of commit history, team contributions, and code-quality signals to produce a structured, team-aware retrospective.

Core Features & Use Cases

  • Team-aware insights: identifies the user running the retro and surfaces per-person praise and growth opportunities for every contributor.
  • Time-bound analysis: supports windows like 7d (default), 24h, 14d, 30d, and a compare mode to highlight trends.
  • Narrative output for teams: generates a Telegram-ready, human-friendly narrative plus a data-backed metrics section.
  • Use cases include weekly sprints, engineering retrospectives after a release, and uptime of code quality reviews.

Quick Start

Run the retro for the default 7-day window to produce a team-ready narrative with per-author praise and growth notes.

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 using git commit history?▼

Automate engineering retrospectives by analyzing git commit history, per-author contributions, and code quality signals to generate a structured team retrospective with individual praise and growth notes.

Can I run a code quality retrospective for different time windows like 24 hours or 30 days?▼

Yes, engineering retrospectives support time-bound analysis windows including 7 days by default, plus 24 hours, 14 days, and 30 days, with a compare mode to highlight contributor trends.

How does a team-aware retrospective identify per-person engineering contributions?▼

A team-aware retrospective identifies the user running the analysis and surfaces per-person contributions by evaluating individual commit history and code quality signals to generate targeted praise and growth opportunities.

What is the best way to generate a Telegram-ready narrative for engineering team retrospectives?▼

Generate a Telegram-ready narrative for engineering retrospectives by synthesizing commit history and code quality metrics into a human-friendly report paired with a structured, data-backed metrics section.

Does the retrospective analysis store persistent history to compare engineering metrics across weeks?▼

Yes, retrospective analysis stores persistent history in memory with deltas across windows, allowing you to compare engineering metrics and team momentum trends over time.

Related Skills

Explore More Software Engineering Skills→
kunalrawat425kunalrawat425

gstack-openclaw-retro

Aggregate commit history, PR activity, and quality metrics into weekly engineering retrospectives.

Community
Advanced
abhishekmmgnabhishekmmgn

gstack-openclaw-retro

Analyze git history to generate team retrospectives with per-person contributions.

Community
Advanced
garrytangarrytan
127.1k

gstack-openclaw-retro

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

Community
Advanced
sadie100sadie100

retro

Analyze commit history, work patterns, and code quality metrics for weekly retrospectives.

Community
Advanced