retro

Analyze commit history and per-author contributions to generate a week-long retrospective.

1|2|Updated Jan 4, 2024

Search Tags:#git #analytics #metrics #engineering #code-quality #retro #team-feedback

Ready to run

npx skills add https://github.com/NaKMiers/Port4lio --skill retro-nakmiers

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/NaKMiers/Port4lio/tree/main/.agents/skills/retro
Command: npx skills add https://github.com/NaKMiers/Port4lio --skill retro-nakmiers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This summary helps engineering teams reflect on past work by aggregating commit history, per-person contributions, and code-quality signals into a concise, actionable retrospective.

Core Features & Use Cases

Team-aware retrospectives with per-person praise and growth areas
Analyzes commit history, PR activity, and hotspots to surface actionable insights
Supports weekly, sprint-window, and global retrospectives across projects

Quick Start

Type /retro to generate the current week's retrospective for the default 7-day window.

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 commit history?▼

To generate an engineering retrospective from git commit history, you can use a tool that analyzes per-author contributions and code-quality signals to produce a team-aware weekly summary. It aggregates repository data into actionable insights.

How does analyzing code-quality signals improve weekly sprint retrospectives?▼

Analyzing code-quality signals improves weekly sprint retrospectives by surfacing specific hotspots and PR activity patterns. This allows teams to move beyond subjective memories and base their reflections on concrete repository metrics.

Can I run a retrospective across multiple projects instead of just a single repository?▼

Yes, you can run a retrospective across multiple projects. The tool supports global retrospectives that aggregate commit history and per-author contributions across different repositories to provide a comprehensive team overview.

What is the best way to surface per-author praise and growth areas in a team retro?▼

The best way to surface per-author praise and growth areas is to analyze individual commit contributions and code-quality metrics. This creates a structured narrative that highlights specific achievements and targeted growth opportunities.

How do I adjust the time window for a sprint retrospective analysis?▼

You can adjust the time window for a sprint retrospective analysis by specifying a custom compare window. While the default generates a 7-day retrospective, the tool supports configurable sprint windows to match your team's cadence.

Does this team retrospective tool require any external dependencies to calculate metrics?▼

No, this team retrospective tool does not require external dependencies to calculate metrics. It relies entirely on built-in repository data analysis to process commit history and code-quality signals into a structured narrative.