Analyze weekly git history to generate retrospective insights and trend analyses.
npx skills add https://github.com/anishs1207/agentic-cli --skill retro-anishs1207
Please help me install this Agent Skill. Skill: retro Source: https://github.com/anishs1207/agentic-cli/tree/main/.agents/skills/gstack-retro Command: npx skills add https://github.com/anishs1207/agentic-cli --skill retro-anishs1207
Weekly engineering retrospectives often stall in manual note-taking and fragmented feedback. This Skill analyzes commit history, team contributions, and process signals to produce a coherent, actionable weekly retrospective with praise and growth opportunities, plus a persistent history for trend tracking.
Run the retro for the past 7 days to generate a team-facing summary with per-person praise, growth opportunities, and trend insights.
High-intent search queries and answers about installing and using this skill.
You can automate engineering retrospectives by analyzing git commit history to surface actionable insights, per-person contributions, and growth areas. This Skill processes repository commits to generate structured metrics and narrative guidance for sprint planning.
An automated weekly sprint retrospective analyzes git history and team performance signals to produce coherent, actionable summaries. It identifies per-person praise, growth opportunities, and trend analyses, replacing manual note-taking with structured metrics and persistent history tracking.
Yes, you can track team performance metrics and trends over time using persistent history generated from weekly git activity analysis. This enables milestone reviews and ongoing process improvements by storing trend data that informs future sprint planning and retrospective guidance.
Yes, a running gstack retro workflow and access to the repository's git history are required to generate retrospective insights. The Skill depends on these to analyze commit history and output structured metrics, per-person contributions, and narrative guidance.
The best way to surface per-person contributions and growth areas from commit history is to run an automated retrospective analysis over a defined period like 7 days. This generates a team-facing summary with individual praise, growth opportunities, and trend insights based on actual commit activity.
You should not use an automated retrospective tool when your repository lacks sufficient git history, when no gstack retro workflow is configured, or when team contributions happen outside the commit stream. The analysis depends entirely on commit data and process signals to generate accurate insights.
borkwebGenerate conventional git commit messages from staged diffs and repository history.
Omar-ObandoFacilitate Scrum ceremonies with timeboxed agendas and impediment tracking.
GTC6244Analyze commit history and code quality metrics to generate weekly team retrospectives.
shekerkammaAnalyze git commit history and code quality metrics to generate weekly engineering retrospective reports.
