retro

Analyze commits, PRs, and tests to generate engineering retrospectives.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives that provide persistent history and trend insights into team work, code quality, and delivery patterns, breaking down contributions for praise and growth.

Core Features & Use Cases

  • Analyzes commit history, PR activity, and test data to surface per-person contributions with actionable growth opportunities.
  • Produces a persistent, trend-aware retrospective across sprints or time windows, enabling team learning and process improvement.
  • Generates a structured plan with focus areas, ship metrics, and concrete next steps for improvement.

Quick Start

Simply request a weekly retro by saying /retro and the system will generate a comprehensive retrospective from your repository data.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate an engineering retrospective from git history and pull requests?

To generate an engineering retrospective from git history, apply this Skill to analyze commits, PRs, and test data. It summarizes software engineering activity to produce a comprehensive retrospective with per-author breakdowns and code quality signals.

What metrics are included in a weekly engineering retro?

A weekly engineering retro includes focus metrics, ship metrics, and per-author contribution breakdowns. It analyzes commits, pull requests, and test data to surface code quality signals and delivery patterns for the configured time window.

Can I track team health and delivery trends across multiple sprints?

Yes, you can track team health and delivery trends across multiple sprints. The Skill produces a persistent, trend-aware retrospective history that enables team learning and process improvement over configurable time windows.

How do I run a post-release review using commit and test data?

Run a post-release review by applying the Skill to your repository data, which evaluates commits, PRs, and tests. It delivers a complete end-to-end plan with concrete next steps and clear visuals for improvement.

Do I need external integrations to extract pull request analytics for my team?

No external integrations are required as the Skill operates without dependencies. It directly analyzes your repository activity to surface pull request analytics and per-person contributions to identify actionable growth opportunities.