retro

Analyzes commit history and work patterns for engineering retrospectives.

1|Updated May 8, 2026
One-click install
npx skills add https://github.com/npc-chris/dfn-discovery --skill retro-npc-chris
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/npc-chris/dfn-discovery/tree/main/.agents/skills/gstack/retro
Command: npx skills add https://github.com/npc-chris/dfn-discovery --skill retro-npc-chris

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, python, and includes scripts (resource) components.

What problem does it solve?

This Skill helps teams perform a comprehensive weekly engineering retrospective by analyzing commit history, work patterns, and code quality metrics.

Core Features & Use Cases

  • Commit History Analysis: Inspects commit logs for insights into work patterns and code quality.
  • Per-Contributor Analysis: Breaks down contributions by individual team members, highlighting praise and growth areas.
  • Time Window Configuration: Allows retrospectives to be performed over customizable time frames (e.g., last 7 days, 14 days, 30 days).
  • Global Retro Option: Offers a cross-project perspective across all AI coding tools.

Quick Start

Execute the /retro command to start the weekly engineering retrospective process.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I perform an engineering retrospective using git commit history?

Analyze git commit history to perform an engineering retrospective by extracting work patterns and code quality metrics. The Skill inspects commit logs to evaluate per-contributor contributions and generate actionable insights over customizable time frames.

What is commit history analysis for team work patterns?

Commit history analysis for team work patterns is the process of inspecting git logs to evaluate individual contributions and code quality trends. It breaks down engineering activity per-contributor to highlight praise and growth areas for improving coding practices.

Can I configure the time frame for a git commit retrospective?

Yes, you can configure the time frame for a git commit retrospective. The analysis supports customizable time windows such as the last 7, 14, or 30 days, allowing you to focus the work pattern and code quality evaluation on your specific reporting period.

Do I need Python and git installed to analyze commit logs?

Yes, you need both Python and git installed to analyze commit logs. These dependencies are required to execute the scripts that parse commit history, evaluate code quality metrics, and generate the per-contributor retrospective insights.

Can I run a cross-project retrospective across multiple AI coding tools?

Yes, you can run a cross-project retrospective across multiple AI coding tools. The global retro option provides a cross-project perspective, aggregating commit history and work pattern analysis beyond a single repository.

What is the best way to analyze per-contributor code quality from git logs?

The best way to analyze per-contributor code quality from git logs is to use a scripted retrospective tool that automatically breaks down contributions by individual team members. This approach highlights specific growth areas and praise points based on commit history metrics.