Summarize git commit history and quality signals into structured retrospectives.
npx skills add https://github.com/cloudofgeorge/AI-hands --skill retro-cloudofgeorge
Please help me install this Agent Skill. Skill: retro Source: https://github.com/cloudofgeorge/AI-hands/tree/main/skills/gstack/retro Command: npx skills add https://github.com/cloudofgeorge/AI-hands --skill retro-cloudofgeorge
Weekly retrospectives summarize engineering work patterns, code activity, and quality signals to help teams reflect and improve.
Run the retro skill at week end to generate a focused engineering retrospective and capture actionable insights.
High-intent search queries and answers about installing and using this skill.
To generate a weekly engineering retrospective, the skill summarizes local git history, project artifacts, and metrics to surface team learnings. It outputs structured retrospectives and a narrative summary for planning.
A git retrospective analyzes commit history and quality signals to reveal engineering growth. It enables per-person contribution analysis, trend tracking, and action-item generation across sprint cycles.
You need access to local git history and project artifacts to run retrospectives. An optional metrics store can be integrated to provide additional quality signals for deeper analysis.
Analyzing per-person contributions for project milestones is best handled by summarizing commit history and timelines. This approach highlights individual patterns and generates concrete action items.
You should run automated retrospectives at week end or after reaching project milestones. This timing captures completed work patterns and generates actionable insights for the next planning phase.
Project artifacts can be used for retrospectives, but combining them with local git history provides a more complete picture. Optional metrics stores add quality signals for comprehensive trend tracking.
grigbAnalyze git history and documentation to extract lessons learned and root causes.
joesysAggregates git history, conversations, code quality, planning docs, and tests into guided retrospective sessions with actionable outcomes.
bajajvinamrAnalyze commit history and work patterns to generate weekly engineering retrospectives.
joshftCompile project health, ROI, and workflow metrics from QA and code data.
