Parse Git commit history to calculate development metrics and identify weekly trends.
npx skills add https://github.com/lmanchu/iris-system --skill retro-lmanchu
Please help me install this Agent Skill. Skill: retro Source: https://github.com/lmanchu/iris-system/tree/main/.claude/skills/gstack/retro Command: npx skills add https://github.com/lmanchu/iris-system --skill retro-lmanchu
This Skill automates the generation of weekly engineering retrospectives, providing deep insights into commit history, work patterns, and code quality to improve team productivity and identify areas for growth.
Run the retro skill to analyze the last 7 days of commits.
High-intent search queries and answers about installing and using this skill.
Automating weekly engineering retrospectives involves parsing Git commit history to calculate development metrics and identify trends. This process provides data-driven insights into team productivity, code quality, and workflow efficiency without manual data gathering.
Yes, you can calculate code quality metrics like test ratio and PR size directly from Git logs. By parsing commit history, the system computes key metrics including lines of code, test ratios, and PR size to evaluate work patterns and quality.
Tracking week-over-week development velocity and commit trends requires parsing Git logs and maintaining a historical record. This approach identifies long-term patterns in author activity and commit frequency to highlight potential bottlenecks or areas of excellence.
Yes, the Git CLI is required to analyze commit history and calculate development metrics. The system relies on Git command-line access to parse logs accurately and requires timezone conversion for precise Pacific time reporting.
The best way to identify workflow bottlenecks using Git commit analysis is to parse commit history and calculate session duration alongside development metrics. This reveals work patterns and highlights areas where team productivity may be restricted.
Timezone conversion matters when parsing Git logs for retrospective analysis because it ensures accurate Pacific time reporting. Converting commit timestamps correctly aligns development metrics and work patterns with the actual working hours of the team.
ericwang915Provide current date, time, timezone, and Unix timestamp conversions.
BaGyun0107Summarizes commit history, code quality, and team contribution patterns over a defined time window.
tranvietanh0Analyze git metrics and generate sprint retrospective reports.
larsnygIdentify and resolve performance bottlenecks across frontend, backend, and database layers.
