Generate weekly engineering retrospectives from git commit history and code quality metrics.
npx skills add https://github.com/a29paul/hexlens --skill retro-a29paul
Please help me install this Agent Skill. Skill: retro Source: https://github.com/a29paul/hexlens/tree/main/.claude/skills/gstack/retro Command: npx skills add https://github.com/a29paul/hexlens --skill retro-a29paul
Manual weekly engineering retrospectives take hours to compile, miss hidden patterns in commit history and work distribution, and fail to track progress or individual growth areas across sprints.
Use the retro skill to generate a weekly engineering retrospective for the current branch, including commit analysis, per-person contribution breakdowns, and trend data from past retros.
High-intent search queries and answers about installing and using this skill.
You can automate a weekly engineering retrospective by parsing git commit history and work patterns to generate team insights, per-person contribution metrics, and code quality trends, replacing manual session preparation.
Yes, you can track sprint-over-sprint engineering trends because the system stores persistent retro history, allowing you to compare progress on code quality, shipping velocity, and team workload across multiple sprints.
The best way to analyze team contributions for a sprint review is automatically parsing commit history to provide per-person metrics, identifying shipped features, bug fixes, and actionable growth areas for each team member.
Yes, you need access to the project's git repository and gstack configuration for session and telemetry management to generate comprehensive retrospectives, with optional integration for project learnings and timeline data.
Automated commit analysis replaces manual sprint reviews by identifying hidden patterns in work distribution and tracking individual growth areas, reducing a two-hour manual review process down to thirty minutes.
Manual retros miss hidden patterns in work distribution because they fail to systematically parse commit history and track code quality metrics, a limitation resolved by data-driven automated retrospective generation.
anilveersingh1308Review, search, prune, and export project learnings from gstack data.
JeremiahEllingtonAnalyze git commit history and work patterns to generate team-wide retrospectives with per-person insights.
yocxy2Track, search, and prune session-based learnings from JSONL logs.
robertzengcnAnalyze git commit history and code quality metrics to generate engineering retrospectives.
