Analyze commit history and code quality metrics to generate weekly team retrospectives.
npx skills add https://github.com/GTC6244/ToolBridge --skill retro-gtc6244
Please help me install this Agent Skill. Skill: retro Source: https://github.com/GTC6244/ToolBridge/tree/main/.claude/skills/gstack/retro Command: npx skills add https://github.com/GTC6244/ToolBridge --skill retro-gtc6244
Weekly engineering retrospectives are hard to assemble from scattered notes. This Skill analyzes commit history, work patterns, and code quality metrics to provide a persistent, team-aware retrospective that highlights praise and growth areas.
Ask Claude to generate the weekly engineering retrospective for the current sprint.
High-intent search queries and answers about installing and using this skill.
To generate a weekly engineering retrospective, analyze commit history, work patterns, and code quality metrics to produce a concise report with per-person insights and trend analysis. This automatically surfaces contributions and growth areas across the team.
A team-aware retrospective tracks developer contributions by analyzing commit history and code quality metrics to highlight individual praise and growth areas. It maintains persistent history to surface velocity and learning trend lines across sprints.
Yes, you can track code quality metrics and work patterns over multiple sprints by maintaining persistent history. This enables data-driven retrospectives by surfacing improvements and trend lines across weekly intervals.
Yes, retrospective analysis applies to engineering teams across multiple projects. It aggregates work patterns and metrics into a unified report, ensuring team-wide insights and per-person contributions are captured regardless of project structure.
Surface per-person growth areas and praise by analyzing individual commit history and code quality metrics. This identifies specific learning opportunities and achievements, providing actionable feedback within the weekly retrospective.
Automate weekly sprint retrospectives by analyzing commit history and code quality metrics directly. This eliminates scattered notes by producing a persistent, team-aware report with actionable insights, per-person feedback, and trend tracking.
garrytanGenerate engineering retrospective reports from git commit history and code quality metrics.
JeremiahEllingtonAnalyze git commit history and work patterns to generate team-wide retrospectives with per-person insights.
bajajvinamrAnalyze commit history and work patterns to generate weekly engineering retrospectives.
RxFitAnalyze Git commit history to generate weekly engineering retrospectives.
