Analyze git commit history to generate a team-aware weekly retrospective.
npx skills add https://github.com/ligianehua/Gstack --skill retro-ligianehua
Please help me install this Agent Skill. Skill: retro Source: https://github.com/ligianehua/Gstack/tree/main/retro Command: npx skills add https://github.com/ligianehua/Gstack --skill retro-ligianehua
Weekly retrospectives are time-consuming and brittle when done manually. This Skill analyzes commit history, work patterns, and code quality metrics to deliver a persistent, team-aware view of what happened, what went well, and where to improve.
Invoke the retro workflow by running the /retro command to generate the latest weekly retrospective for the current repository.
High-intent search queries and answers about installing and using this skill.
This Skill generates a weekly retrospective by analyzing git commit history, work patterns, and code quality metrics to summarize per-author contributions and surface growth opportunities. It requires access to git history and per-commit data to compute individual engineering metrics.
Yes, you can track per-person engineering metrics automatically by analyzing commit history and per-commit data. This Skill computes individual code quality metrics and work patterns to highlight team praise and specific growth opportunities for each author.
To generate team-aware sprint retrospectives from git data, you need access to your repository's git history and per-commit data. This allows the Skill to compute per-author metrics and output a structured retrospective for review and planning.
Analyzing commit history improves sprint retrospectives by providing a persistent, data-driven view of work patterns and code quality metrics, replacing brittle manual reviews. It surfaces historical trends and bottlenecks across sprints to objectively guide team improvement.
Yes, this approach works for tracking historical engineering trends across multiple sprints. It analyzes historical commit data to surface recurring patterns and bottlenecks, proactively suggesting focus areas for continuous team improvement at sprint end.
CarbeneAIGenerate weekly engineering retrospectives from git logs and analytics files.
devCharuzuAnalyze sprint data to forecast velocity and generate health scores.
garrytanGenerate engineering retrospective reports from git commit history and code quality metrics.
ComputerConnectionAnalyze weekly git activity to generate team-aware retrospectives with per-author metrics.
