Aggregate git commit history into weekly team retrospectives with per-person metrics.
npx skills add https://github.com/JonOlsenCa/gstack-main --skill retro-jonolsenca
Please help me install this Agent Skill. Skill: retro Source: https://github.com/JonOlsenCa/gstack-main/tree/main/retro Command: npx skills add https://github.com/JonOlsenCa/gstack-main --skill retro-jonolsenca
Weekly engineering retrospectives that analyze commit history, work patterns, and code quality metrics with historical context to reveal trends, praise, and growth opportunities.
Run /retro to generate a weekly engineering retrospective for the current repository.
High-intent search queries and answers about installing and using this skill.
Generate a weekly engineering retrospective by analyzing git commit history, work patterns, and code quality metrics to track shipping velocity and contributor contributions. Run the /retro command to aggregate repository data and output a structured review.
Yes, team retrospectives can analyze code quality metrics and work patterns across one repo or multiple projects. The analysis provides per-person breakdowns of contributor contributions and identifies growth opportunities for the engineering team.
A git commit history retrospective aggregates commit data to compute metrics, track shipping velocity trends, and surface process improvements. It analyzes historical context to reveal long-term patterns in code quality and collaboration for engineering teams.
Track shipping velocity and contributor contributions by computing metrics from git history to generate a team-focused retrospective. The analysis provides per-person breakdowns, historical trend tracking, and tailored recommendations for future sprints.
Weekly retrospective analysis works with both a single repository and multiple projects. It reads git history from the configured scope and aggregates commit data to compute shipping velocity, code quality, and collaboration metrics for the team.
A git history retrospective proactively surfaces action items at week end by analyzing work patterns and code quality metrics. It provides tailored recommendations for future sprints and identifies growth opportunities for individual contributors.
elithrarAnalyze session history and git state to generate structured commit-message summaries.
akillnessFacilitate structured sprint retrospectives with Start-Stop-Continue, Mad-Sad-Glad, or 4Ls templates.
NoobyGainsEnforce code quality standards across pre-commit, pre-merge, and CI pipeline stages.
yashs33244Generate weekly engineering retrospectives from git commit history and code-quality metrics.
