skills.rest
GrassHopper42
GrassHopper42COMMUNITY
Explore all skills by this author →
WebsiteGitHub

gstack-openclaw-retro

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

Updated Jun 22, 2026
Search Tags:#team contributions#code quality metrics#commit history analysis#engineering retro#retrospective report
One-click install
npx skills add https://github.com/GrassHopper42/ANTidy --skill gstack-openclaw-retro-grasshopper42
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-openclaw-retro
Source: https://github.com/GrassHopper42/ANTidy/tree/main/.claude/skills/gstack/openclaw/skills/gstack-openclaw-retro
Command: npx skills add https://github.com/GrassHopper42/ANTidy --skill gstack-openclaw-retro-grasshopper42

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive weekly engineering retrospective by analyzing commit history, work patterns, and code quality metrics, offering a detailed view of team contributions and growth areas.

Core Features & Use Cases

  • Commit History Analysis: Analyze commit history to understand work patterns and code quality.
  • Team Contributions: Track contributions of each team member with praise and growth areas.
  • Use Case: When preparing a weekly engineering retro, this Skill can generate a report on the last 7 days of work, highlighting the main contributions and identifying areas for improvement.

Quick Start

Generate a weekly engineering retro report for the last 7 days using the command: gstack-openclaw-retro 7d.

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 report from commit history?▼

Generate a weekly engineering retrospective report by analyzing commit history and code quality metrics to track team contributions, identify trends, and provide insights for improvement.

What is engineering retro analysis and how does it track team contributions?▼

Engineering retro analysis evaluates commit history and code quality metrics over a specific period to track individual team member contributions, offering praise and identifying growth areas.

Do I need git installed to analyze code quality metrics for a retrospective?▼

Yes, you need git and various data extraction tools installed locally to analyze commit history and generate the weekly engineering retrospective report.

What's the best way to analyze the last 7 days of work patterns for a team retro?▼

Analyze the last 7 days of work patterns by running the command `gstack-openclaw-retro 7d`, which automatically extracts commit history and code quality metrics.

Can I use commit history analysis to identify growth areas for specific team members?▼

Yes, commit history analysis tracks contributions of each team member to highlight main contributions and identify specific areas for improvement during the retrospective.

Related Skills

Explore More Software Engineering Skills→
garrytangarrytan
127.1k

gstack-openclaw-retro

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

Community
Advanced
AlejandroFiginiAlejandroFigini

retro

Analyze commit history and code quality trends to generate weekly retrospective summaries.

Community
Intermediate
SandroBeatzSandroBeatz

lint-check

Run ESLint and TypeScript type checking on a codebase.

Community
Intermediate
ManzuetiManzueti

retro

Generate engineering retrospective reports from commit history and work patterns.

Community
Advanced