skills.rest
simbotNL
simbotNLCOMMUNITY
Explore all skills by this author →
GitHub

gstack-openclaw-retro

Analyze commit history and code quality metrics for engineering retrospectives.

Updated Aug 23, 2026
Search Tags:#code quality#commit history#team analysis#work patterns#engineering retro
One-click install
npx skills add https://github.com/simbotNL/BT --skill gstack-openclaw-retro-simbotnl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-openclaw-retro
Source: https://github.com/simbotNL/BT/tree/main/plugins/gstack/openclaw/skills/gstack-openclaw-retro
Command: npx skills add https://github.com/simbotNL/BT --skill gstack-openclaw-retro-simbotnl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, python, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the analysis of commit history, work patterns, and code quality metrics for weekly engineering retrospectives, providing insights into team performance and individual contributions.

Core Features & Use Cases

  • Commit History Analysis: Analyze commit history for patterns, frequency, and code quality.
  • Work Pattern Insights: Identify peak coding hours, session lengths, and focus areas.
  • Team Member Analysis: Evaluate individual contributions, praise, and growth areas.
  • Use Case: Use this Skill to generate a comprehensive report for a weekly engineering retro, including metrics on commits, pull requests, and code changes.

Quick Start

Run the gstack-openclaw-retro skill to generate a weekly engineering retro 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 analyze commit history and work patterns for an engineering retrospective?▼

Analyzing commit history for an engineering retro involves processing git repository data to identify team members, commits, pull requests, and code changes over a specified time window. This skill automates that data extraction to evaluate team performance and individual contributions.

What metrics are included in a weekly engineering retro report?▼

A weekly engineering retro report includes metrics on commit frequency, code quality, pull requests, and code changes. It identifies peak coding hours, session lengths, and focus areas to provide insights into team performance and individual growth areas.

Do I need git installed to analyze code quality and team contributions?▼

Yes, you need git installed to access repository history for analyzing code quality and team contributions. Python is also required as a dependency to process the data analysis tools and present the retrospective results.

Can I evaluate individual developer contributions from pull request data?▼

Yes, you can evaluate individual developer contributions by analyzing pull request data and commit history. The skill processes these metrics to highlight individual praise, growth areas, and specific code changes made during the specified time window.

How do I generate a report for the last 7 days of repository activity?▼

To generate a report for the last 7 days of repository activity, run the skill to analyze the commit history over that specified time window. It will process the git data and output a comprehensive report of work patterns and code quality metrics.

Related Skills

Explore More Software Engineering Skills→
cegit27cegit27
3

retro

Analyze git commit history to generate weekly retrospective reports.

Official
Advanced
zz8011zz8011

retro

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

Community
Advanced
seanyofthedeadseanyofthedead

systematic-code-review

Automate a 4-phase code review process for pull requests.

Community
Advanced
smarmen86smarmen86

retro

Generates engineering retrospectives from git commit history and timeline events.

Community
Advanced