gstack-openclaw-retro

Summarizes commit history, code quality, and team contribution patterns over a defined time window.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/BaGyun0107/harness-starterkit --skill gstack-openclaw-retro-bagyun0107
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-openclaw-retro
Source: https://github.com/BaGyun0107/harness-starterkit/tree/main/.claude/skills/gstack/openclaw/skills/gstack-openclaw-retro
Command: npx skills add https://github.com/BaGyun0107/harness-starterkit --skill gstack-openclaw-retro-bagyun0107

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Developers and teams need an organized way to analyze their recent code activity, identify trends, and track contributions efficiently.

Core Features & Use Cases

  • Automated Retro Generation: analyzes commit history, PRs, and code quality metrics over a specified period.
  • Team and Personal Insights: provides detailed summaries of individual contributions, session patterns, and code hotspots.
  • Use Case: A team runs this Skill weekly to get a comprehensive overview of their development cycle, spotting bottlenecks and celebrating key achievements.

Quick Start

Run the retro analysis to generate a weekly report summarizing recent commits, contributions, and code health metrics.

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 with git log analysis?

Automate weekly engineering retrospectives by analyzing commit history, PR references, and code quality metrics over a specified time window to generate a comprehensive team development report.

What is commit analysis for team metrics and trend tracking?

Commit analysis for team metrics summarizes recent development activity, identifying individual contribution patterns, code hotspots, and collaboration trends to track ongoing codebase health.

Does this retrospective tool require specific code analysis tools to run?

Yes, generating comprehensive retrospective reports requires git log data, PR references, and code analysis tools to evaluate codebase contributions and code quality effectively.

Can I get detailed personal contribution insights from my commit history?

Yes, you can get detailed personal insights from commit history, as the analysis provides summaries of individual contributions, session patterns, and specific code hotspots.

What is the best way to track code quality trends over a defined time window?

The best way to track code quality trends is by running weekly retrospective analysis over a defined time window, which spots bottlenecks, tracks metrics, and celebrates achievements.