Generate weekly engineering retrospectives from local project activity and team contributions.
npx skills add https://github.com/mi179/claude-skills --skill retro-mi179
Please help me install this Agent Skill. Skill: retro Source: https://github.com/mi179/claude-skills/tree/main/user/gstack/retro Command: npx skills add https://github.com/mi179/claude-skills --skill retro-mi179
Weekly engineering retrospectives help teams review past work, surface contributions, and identify growth opportunities with persistent history and trend tracking across sprints.
Ask the retro skill to generate a weekly retrospective for the current sprint.
High-intent search queries and answers about installing and using this skill.
To generate a weekly engineering retrospective, the skill analyzes project activity, commit history, and team contributions to produce per-person praise and growth areas. It requires local retrospective files stored under the gstack projects directory to render historical context.
Tracking engineering team performance across sprints requires analyzing persistent retrospective history and timelines. This skill maintains a persistent backlog of retrospectives to track progress over time, surfacing actionable insights and per-person contributions from prior project activity.
Analyzing commit history and timelines for sprint reviews involves reading prior retros and learnings files to extract per-person contributions. The skill processes this local project data to highlight individual praise and identify specific growth areas for the team.
Yes, storing project retrospectives requires a specific local directory structure. You need local retrospectives stored under the gstack projects path for the repository slug, which the skill reads to render historical context and track performance trends.
Yes, you can review individual and team performance contributions from prior sprints. The skill reads stored retrospective history and timeline files to break down per-person contributions, providing a comprehensive overview of past project activity and growth opportunities.
A key limitation for tracking retrospective trends is the dependency on local history files. If prior retros, timelines, or learnings files are missing from the gstack projects directory, the skill cannot render full historical context or accurately track long-term team performance.
abhishekmmgnGenerate structured weekly retrospective narratives from git history, timelines, and learnings.
JeremiahEllingtonAnalyze git commit history and work patterns to generate team-wide retrospectives with per-person insights.
cloudofgeorgeSummarize git commit history and quality signals into structured retrospectives.
256javyAggregate commit history and code quality metrics into weekly engineering retrospectives.
