retro

Summarize weekly engineering activity into structured retro reports from git and test data.

Updated Apr 11, 2026

Search Tags:#git #metrics #engineering #retro #weekly #team-performance

Ready to run

npx skills add https://github.com/akiyoshi/gstack-copilot-jp --skill retro-akiyoshi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/akiyoshi/gstack-copilot-jp/tree/main/.github/skills/retro
Command: npx skills add https://github.com/akiyoshi/gstack-copilot-jp --skill retro-akiyoshi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives for engineering teams help surface actionable insights from code, tests, and collaboration data, enabling data-driven improvements.

Core Features & Use Cases

Generate a comprehensive weekly engineering retrospective including commits, test health, hotspots, and team patterns.
Provide per-contributor analysis, focus scores, and ship-of-the-week highlights to guide improvements.
Use for sprint reviews, post-release audits, and planning conversations.

Quick Start

Run the retro workflow for the current project to generate a weekly report and actionable insights.

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 git activity?▼

To generate a weekly engineering retrospective, this Skill summarizes git commits, test health, and team patterns into a structured narrative report. It collects data across repo time windows to surface actionable insights for sprint reviews and planning conversations.

What is included in an engineering team performance report?▼

An engineering team performance report includes per-author analysis, focus scores, ship-of-the-week highlights, and code hotspots. It aggregates git metrics and test files to provide a comprehensive view of weekly engineering health and growth.

Can I run a retrospective report across multiple time windows like 7d or 30d?▼

Yes, you can run retrospective reports across 7d, 14d, and 30d time windows. The Skill applies these periods to git data to offer both repo-scoped and global retrospectives for tracking engineering health over different intervals.

Does the weekly retro report support individual contributor analysis?▼

Yes, the weekly retro report supports individual contributor analysis by providing per-author metrics and focus scores. This helps identify individual patterns and guide team improvements during post-release audits and reviews.

What is the best way to track engineering health and growth for sprint reviews?▼

The best way to track engineering health is by generating a JSON snapshot of weekly activity and presenting a narrative report. This approach surfaces commits, test health, and hotspots suitable for team reviews and data-driven improvements.