Generate weekly or cross-project engineering retrospectives from git history and contributor activity.
npx skills add https://github.com/24601/gastack-pre-fork --skill retro-24601
Please help me install this Agent Skill. Skill: retro Source: https://github.com/24601/gastack-pre-fork/tree/main/retro Command: npx skills add https://github.com/24601/gastack-pre-fork --skill retro-24601
The retro skill automates the collection and synthesis of engineering history — turning commit data, participation, and quality signals into an actionable weekly or cross-project retrospective.
Run /retro to generate a weekly or global retrospective for the current project.
High-intent search queries and answers about installing and using this skill.
To generate a weekly engineering retrospective, the retro skill summarizes your repository's git history and contributor activity, extracting per-person contributions and quality signals into a structured narrative. It requires access to local git history and project analytics data.
A multi-repo retrospective analyzes contributor activity and commit data across multiple repositories simultaneously. The retro skill's global mode synthesizes cross-project engineering history to highlight patterns and growth opportunities across your entire codebase.
Yes, git analytics can track per-person contributions and growth opportunities for sprint reviews. The retro skill extracts participation data and quality signals from commit history to produce team-aware narratives and persistent trend tracking for sprint-end reviews.
You need access to local git history and project analytics data to run an automated code retrospective. Optional telemetry can also be integrated to enhance the structured metrics and narrative output for leadership reviews.
The best way to summarize contributor activity patterns across multiple AI coding tools is using a global retro mode. This approach analyzes cross-project engineering history to produce team-aware narratives that highlight participation trends and growth opportunities.
Your engineering retrospective needs persistent history and trend tracking to identify long-term patterns in contributor activity and code quality. This enables team-aware narratives that reveal growth opportunities and participation trends across weekly sprints or multi-project reviews.
abhishekmmgnGenerate structured weekly retrospective narratives from git history, timelines, and learnings.
andrew-t-jamesAnalyze the last 7 days of commits to generate a structured team retrospective.
KrismithReddy12Analyze engineering commit history and project timeline data to generate automated retrospective reports.
singhianand23045Analyze Git commit history to generate weekly engineering retrospectives with per-author praise.
