Analyze commit history and code quality metrics to generate weekly engineering retrospectives.
npx skills add https://github.com/mgher668/surf-ai --skill retro-mgher668
Please help me install this Agent Skill. Skill: retro Source: https://github.com/mgher668/surf-ai/tree/main/.agents/skills/gstack/retro Command: npx skills add https://github.com/mgher668/surf-ai --skill retro-mgher668
Weekly retrospectives are hard to correlate with code history and team dynamics. This Skill automates the generation of a structured engineering retrospective by analyzing commit history, work patterns, and code quality metrics, delivering a clear, actionable narrative for the team.
Ask me for a weekly retro with /retro and I will generate the report.
High-intent search queries and answers about installing and using this skill.
Automating a weekly engineering retrospective analyzes commit history and code quality metrics to generate a structured report with per-person praise and growth areas. It correlates code history with team dynamics to produce an actionable narrative.
Tracking engineering growth across sprints requires persistent history to show improvement over time. This approach maintains trend tracking across weeks, delivering team-aware summaries that highlight continuous code quality and contribution patterns.
Team-aware analysis breaks down per-person contributions by evaluating commit history and work patterns, then generating specific praise and targeted growth opportunities for each developer within the weekly retrospective.
Generating code quality retrospectives requires no external dependencies. The process integrates directly with Claude workflows, using commit history and work pattern data to produce context-aware outputs for weekly sprints.
The best way to summarize what your team shipped is by analyzing commit history and code quality metrics to generate a structured engineering retrospective. This delivers a clear, actionable narrative covering work patterns and team dynamics.
Generating a retro report for project teams involves analyzing commit history and code quality metrics to produce a weekly engineering retrospective. The output provides team-wide insights with per-person praise and growth opportunities.
nuurproAnalyze local git history to summarize weekly engineering activity and suggest next-sprint focus areas.
JeremiahEllingtonAnalyze git commit history and work patterns to generate team-wide retrospectives with per-person insights.
256javyAggregate commit history and code quality metrics into weekly engineering retrospectives.
scanbottAnalyze commit history and work patterns to summarize weekly engineering performance.
