skills.rest
kunalrawat425
kunalrawat425COMMUNITY
Explore all skills by this author →
GitHub

gstack-openclaw-retro

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives compile and analyze engineering activity, turning raw commit and code-quality data into actionable team insights, praise, and growth opportunities.

Core Features & Use Cases

  • Team-wide retrospectives that aggregate commit history, PR activity, and contributor metrics to reveal trends.
  • Per-person insights highlighting praise and growth opportunities tailored to each contributor.
  • Persistent history and trend tracking across cycles to monitor improvement over time.

Quick Start

Simply command the retro engine to generate the weekly retro for the current window and view the 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 generate a weekly engineering retrospective from git history and PR activity?▼

Generate a weekly engineering retrospective by aggregating git commit history and PR activity to analyze contributor metrics, surfacing per-person praise and growth opportunities in a narrative format.

What is a team-aware engineering retro and how does it analyze contributors?▼

A team-aware engineering retro analyzes the current user and all contributors within a specific time window, processing individual commit and PR data to generate tailored per-person insights and team-wide trends.

Can I use commit and PR metrics to track engineering team improvement over time?▼

Yes, you can track engineering team improvement over time by utilizing persistent history and trend tracking across retrospective cycles to monitor contributor growth and quality metrics.

How do I output engineering analysis results as a Telegram narrative?▼

Output engineering analysis results as a Telegram narrative by processing aggregated commit history and code-quality data, which produces a readable narrative suitable for direct Telegram delivery.

Does the weekly retro analysis require specific code-quality tools to function?▼

The weekly retro analysis aggregates existing commit history and code-quality metrics, requiring no specific external code-quality tools or dependencies to generate its retrospective narrative.

Related Skills

Explore More Software Engineering Skills→
imonmiimonmi

retro

Analyze weekly commit history and code quality for team retrospectives.

Community
Advanced
shekerkammashekerkamma

retro

Analyze git commit history and code quality metrics to generate weekly engineering retrospective reports.

Community
Advanced
koderoverkoderover
7

sonar

Retrieve and analyze SonarQube code quality metrics and quality gate statuses.

Official
Intermediate
Mohamed-ElkahefMohamed-Elkahef

dashboard-creation

Build interactive analytics dashboards with Chart.js for business metrics and KPIs.

Community
Advanced