gstack-openclaw-retro

To analyze git commit history for a weekly engineering retrospective, you can run the skill with a specified time window like '7d'. It fetches repository data using git log and git shortlog to generate a detailed report on team performance and code health.

Git work pattern analysis evaluates team performance by reviewing commit history to identify individual contributions, praise, and growth areas. It provides a comprehensive overview of work patterns and code quality metrics over a specified time period.

Yes, you can review code quality metrics from a local git repository. The skill requires git installed in your environment to fetch and analyze commit data, evaluating code health and team contributions for your retrospectives.

You need git installed to run a repository retrospective. The skill depends on git and utilizes various built-in git commands like git log and git shortlog to fetch and analyze the required commit history and work pattern data.

The best way to generate a team performance report from recent commits is to execute the skill with a time window argument, such as '7d'. It automatically analyzes work patterns and code quality metrics to output a detailed retrospective report.

Using git log data for code quality analysis limits the evaluation to commit history patterns and metadata. The retrospective relies on git commands to infer team performance and code health, meaning it may not capture uncommitted local changes or external code review feedback.