Aggregate commit history and code quality metrics into weekly engineering retrospectives.
npx skills add https://github.com/256javy/safia --skill retro-256javy
Please help me install this Agent Skill. Skill: retro Source: https://github.com/256javy/safia/tree/main/.claude/skills/gstack/retro Command: npx skills add https://github.com/256javy/safia --skill retro-256javy
Weekly engineering retrospectives are time-consuming to compile and hard to surface actionable insights. This skill analyzes commit history, work patterns, and code quality metrics to provide a persistent retrospective history with trend tracking and per-person growth notes.
Summarize this week's work and produce a retro for the current sprint using the repository data.
High-intent search queries and answers about installing and using this skill.
To generate a weekly engineering retrospective, aggregate commit history, work patterns, and code quality metrics to summarize shipped work, growth areas, and per-person contributions. This provides a persistent retro history with trend tracking.
An engineering retrospective should include commit history, work patterns, and code quality metrics. These metrics surface per-person contributions, highlight growth areas, and enable trend tracking across sprints.
Yes, code quality metrics combined with commit history and work patterns are used to produce team-aware summaries. This breaks down individual contributions and identifies specific praise and growth areas for each team member.
The best way to track engineering trends is by maintaining a persistent history of weekly retrospectives. Aggregating work patterns and code quality metrics over time generates trend tracking and proactive growth suggestions.
Automated engineering retros focus on team-aware breakdowns but also provide per-person growth notes. Analyzing individual commit history and code quality metrics highlights specific praise and growth areas for each developer.
ericdahl-devGenerate weekly engineering retrospectives from git commit history and code quality metrics.
JeremiahEllingtonAnalyze git commit history and work patterns to generate team-wide retrospectives with per-person insights.
shekerkammaAnalyze git commit history and code quality metrics to generate weekly engineering retrospective reports.
yocxy2Analyze commit history and work patterns to generate engineering retrospective reports.
