Generate structured engineering retros from commit history and code-quality signals.
npx skills add https://github.com/vnmoorthy/Skylog --skill retro-vnmoorthy
Please help me install this Agent Skill. Skill: retro Source: https://github.com/vnmoorthy/Skylog/tree/main/.claude/skills/gstack/retro Command: npx skills add https://github.com/vnmoorthy/Skylog --skill retro-vnmoorthy
Weekly engineering retro analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking to help teams reflect and improve.
Prompt the retro with a request to summarize the latest sprint, highlight key learnings, and suggest actionable next steps.
High-intent search queries and answers about installing and using this skill.
Generating an engineering retrospective from git commit history involves analyzing recent commits, work patterns, and code-quality signals to produce a structured review of what shipped. The process surfaces per-person contributions and actionable growth opportunities for the team.
Tracking sprint velocity and team performance trends requires persistent history to detect patterns across multiple sprints. Analyzing commit data over time identifies recurring patterns in engineering velocity, code quality, and team collaboration to guide continuous improvement.
Automated code-quality signal analysis works by parsing recent git commits and work patterns to extract quality metrics. It structures these signals into a retrospective format, highlighting key learnings and suggesting actionable next steps for the engineering team.
Yes, you can use git retrospective analysis to generate per-person contribution breakdowns. It evaluates individual commits to surface specific praise and growth areas, helping teams recognize individual value and identify targeted development opportunities.
You need to run a retrospective on recent commits at the end of a sprint or week. Proactive retrospective prompts align with ongoing project cycles, keeping the team synchronized whenever a development milestone is reached or code is shipped.
No specific dependencies or components are required to run the retrospective analysis. It operates independently to process git history and work patterns, generating structured engineering insights without needing external modules or setup.
ISAQQSAIAnalyze Git repositories to generate developer portraits from commit habits and work patterns.
legotec73Analyzes weekly engineering activity from commit history, PR cadence, and quality signals to produce a retrospective.
ericdahl-devGenerate weekly engineering retrospectives from git commit history and code quality metrics.
HouseofmvpsAnalyze git repository history to generate structured sprint retrospective reports.
