skills.rest
moogieon
moogieonCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gstack-openclaw-retro

Analyze git commit history and code quality metrics for engineering retrospectives.

Updated Jun 19, 2026
Search Tags:#code quality#commit analysis#work patterns#engineering retro#team insights
One-click install
npx skills add https://github.com/moogieon/kadera --skill gstack-openclaw-retro-moogieon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-openclaw-retro
Source: https://github.com/moogieon/kadera/tree/main/.claude/skills/gstack/openclaw/skills/gstack-openclaw-retro
Command: npx skills add https://github.com/moogieon/kadera --skill gstack-openclaw-retro-moogieon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the process of conducting weekly engineering retrospectives by analyzing commit history, work patterns, and code quality metrics, providing a comprehensive overview of team contributions and performance.

Core Features & Use Cases

  • Commit History Analysis: Analyzes commit history to provide insights into work patterns and code quality.
  • Team Awareness: Identifies team members and provides per-person contributions, praise, and growth areas.
  • Use Case: Use this Skill to generate a weekly engineering retrospective report that includes commit metrics, session patterns, and team member analyses.

Quick Start

Run the gstack-openclaw-retro skill to generate a weekly engineering retrospective report 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 weekly engineering retrospectives using git commit history?▼

Engineering retrospectives can be automated by analyzing commit history, work patterns, and code quality metrics to automatically generate a comprehensive weekly report detailing team contributions and performance.

What metrics are included in a commit analysis for team insights?▼

Commit analysis for team insights includes individual team member contributions, session patterns, and code quality metrics, providing specific data on praise and growth areas for each person.

Can I use git log commands to track individual developer contributions for a retro?▼

Yes, you can use git log commands to retrieve commit data for engineering retrospectives. The Skill requires git log commands for data retrieval to identify team members and assess individual contributions.

Does generating a team retro report require any special setup?▼

Generating a team retro report requires no special setup or dependencies. You simply run the Skill to analyze the last 7 days of commit history and work patterns to produce the retrospective report.

What is the best way to analyze code quality and work patterns for a development team?▼

The best way to analyze code quality and work patterns is to automate the process by parsing commit history metrics. This method identifies team members and tracks session patterns to provide a comprehensive performance overview.

Why does my engineering retrospective only cover the last 7 days?▼

Your engineering retrospective covers the last 7 days because the Skill is designed to generate a weekly report. It analyzes the commit history and work patterns specifically from the previous week to provide timely team insights.

Related Skills

Explore More Software Engineering Skills→
gufrancogufranco
11

commit

Analyze uncommitted Git changes and generate conventional commit messages.

Community
Intermediate
ManzuetiManzueti

retro

Generate engineering retrospective reports from commit history and work patterns.

Community
Advanced
michsindlingermichsindlinger
1

Quality Metrics Skill

Automate code quality tracking and reporting across CI/CD pipelines.

Community
Advanced
yocxy2yocxy2

gstack-openclaw-retro

Analyze git commit history to generate engineering retrospectives.

Community
Advanced