Generates weekly engineering retrospectives from commit history and code quality metrics.
npx skills add https://github.com/chriswestt/claude-skills --skill retro-chriswestt
Please help me install this Agent Skill. Skill: retro Source: https://github.com/chriswestt/claude-skills/tree/main/gstack/retro Command: npx skills add https://github.com/chriswestt/claude-skills --skill retro-chriswestt
Weekly engineering retrospective. 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.
Tell Claude to run a weekly retro for the current sprint and summarize the week's commits, patterns, and growth opportunities.
High-intent search queries and answers about installing and using this skill.
To generate a weekly engineering retrospective, the Skill analyzes commit history, work patterns, and code quality metrics to summarize what shipped and highlight growth areas. It requires access to repository data and team context to produce accurate, team-aware insights.
Yes, you can track team performance and growth trends over multiple sprints using persistent history. The Skill maintains a running record of code quality metrics and per-person contributions to show improvement or regression over time.
The best way to analyze per-person code quality and work patterns is by breaking down individual contributions during a weekly review. The Skill highlights collaboration patterns, offering specific praise and identifying growth opportunities for each team member.
Yes, you need repository data, historical metrics, and team context to run an accurate sprint retrospective. The Skill relies on this access to analyze commit history and generate team-aware insights for your weekly review.
An automated sprint retrospective for engineering teams includes a summary of what shipped, what work patterns emerged, and where to improve. It breaks down per-person contributions with specific praise and actionable growth areas based on commit history.
thanh-abaiiAnalyze commit history and code quality metrics to create engineering retrospective reports.
GTC6244Analyze commit history and code quality metrics to generate weekly team retrospectives.
michsindlingerAutomate code quality tracking and reporting across CI/CD pipelines.
tygwanControl sprint lifecycles and track velocity and burndown metrics.
