Analyze commit history and code quality metrics to generate weekly engineering retro summaries.
npx skills add https://github.com/MissTully/Gstack --skill retro-misstully
Please help me install this Agent Skill. Skill: retro Source: https://github.com/MissTully/Gstack/tree/main/retro Command: npx skills add https://github.com/MissTully/Gstack --skill retro-misstully
Weekly engineering retrospective that analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas.
Ask Claude to run a weekly retro on the current sprint to generate a team retrospective and growth plan.
High-intent search queries and answers about installing and using this skill.
To generate an engineering retrospective from git history, the Skill analyzes commit logs, work patterns, and code quality metrics to produce team-wide summaries and per-person growth notes for sprint reviews.
A team-wide engineering retro analyzes commit history, work patterns, and code quality metrics. It breaks down per-person contributions, highlighting praise and growth areas to identify team improvement areas.
Run a weekly retro by asking Claude to analyze the current sprint. The Skill requires access to a project's git history, a persistent history store, and the gstack runtime to produce actionable retro guidance.
Yes, a persistent history store is required for sprint-end reviews. It enables trend tracking across weekly retros, allowing the Skill to compare past and current code quality metrics to generate actionable growth plans.
Yes, you can automate engineering retros to close feedback loops. The Skill proactively suggests action items at the end of a work week or sprint, applying team-aware analysis to generate per-person growth notes.
No, the retro Skill requires the gstack runtime to function. Alongside gstack, it needs access to a project's git history and a persistent history store to process work patterns and generate retrospective guidance.
KrismithReddy12Analyze engineering commit history and project timeline data to generate automated retrospective reports.
BradliebsAnalyze commit history and work patterns to generate weekly engineering retrospectives.
devs6186Analyze commit history and quality metrics to generate team-aware retrospectives.
scanbottAnalyze commit history and work patterns to summarize weekly engineering performance.
