retro

Analyze commit history and work patterns to generate weekly engineering retrospectives.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Bradliebs/VolumeTurtle --skill retro-bradliebs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/Bradliebs/VolumeTurtle/tree/main/.gstack/retro
Command: npx skills add https://github.com/Bradliebs/VolumeTurtle --skill retro-bradliebs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives that consolidate commit history, work patterns, and code-quality signals into a persistent, team-aware view.

Core Features & Use Cases

  • Per-person contributions with praise and growth areas to guide individual development.
  • Longitudinal metrics and trend tracking across sprints to surface improvements.
  • Automated retrospective generation and summaries for sprint reviews and planning.

Quick Start

Provide your week's activity data so the retrospective can be generated.

Frequently Asked Questions about retro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a weekly engineering retrospective from commit history?

To generate a weekly engineering retrospective, you provide your week's activity data so the tool can analyze commit history, work patterns, and code quality to produce a persistent, team-aware summary of process health and individual contributions.

What is the best way to track code quality and team performance across multiple sprints?

Tracking code quality and team performance across multiple sprints requires applying longitudinal metrics analysis to your project history, which reveals per-person contributions, growth areas, and overall process health trends suitable for sprint planning.

Can I use automated retrospective summaries for sprint planning and reviews?

Yes, you can use automated retrospective summaries for sprint planning and reviews because the analysis satisfies requirements for persistent history, clear summaries, and actionable insights derived from your commit history and work patterns.

How do engineering retrospectives identify per-person contributions and growth areas?

Engineering retrospectives identify per-person contributions and growth areas by analyzing commit history and work patterns, consolidating these code-quality signals into a team-aware view that highlights individual development needs.

Do I need to provide specific activity data formats to run a code quality retrospective?

To run a code quality retrospective, you simply provide your week's activity data so the analysis can process your commit history and work patterns to generate the engineering retrospective without requiring specific external dependencies.