Analyze commit history and code metrics to generate weekly team retrospectives.
npx skills add https://github.com/tropeks/Vitali --skill retro-tropeks
Please help me install this Agent Skill. Skill: retro Source: https://github.com/tropeks/Vitali/tree/main/.claude/skills/gstack-retro Command: npx skills add https://github.com/tropeks/Vitali --skill retro-tropeks
Weekly engineering retrospectives are hard to assemble from scattered notes, making it difficult for teams to surface what shipped, what didn’t, and why. This Skill consolidates commit history, code quality metrics, and collaboration signals into a concise, actionable retrospective.
/retro to generate a team-wide report showing top contributors, hotspot files, and suggested focus areas.Run /retro to generate the weekly retrospective for the current project and time window.
High-intent search queries and answers about installing and using this skill.
Generate a weekly engineering retrospective by analyzing git commit history, code quality metrics, and collaboration signals to surface per-author contributions, hotspot files, and recommended improvements. Running the retro command produces a team-aware report ready for leadership review.
Yes, retrospectives can be applied to both single-repo and cross-project contexts to surface who shipped, hotspots, and growth opportunities across the team. Cross-project comparisons guide planning and process improvements using persistent trend tracking history.
A team-aware engineering retrospective includes per-author contributions, focus areas, commit activity, test results, hotspot files, and collaboration signals. It derives per-contributor praise and growth opportunities to provide an end-to-end narrative with clear guardrails for leadership review.
Track engineering team performance trends by running retrospectives that maintain persistent history with trend tracking and cross-project comparisons. This consolidates scattered notes and metrics to guide planning, showing top contributors and suggested focus areas over time.
Prepare a leadership-ready engineering report by running a retrospective that analyzes commit history and collaboration signals to produce an end-to-end narrative. The report includes per-contributor praise, growth opportunities, and recommended improvements with clear guardrails.
viraatdasAnalyze git commit history and contribution metrics to generate weekly team retrospectives.
SeaLion-hubAnalyze commit history and contribution patterns to generate weekly engineering retrospective reports.
borkwebGenerate conventional git commit messages from staged diffs and repository history.
SeongHuniGenerate sprint or milestone retrospectives by analyzing project data.