retrospective

Correlate git commit history with planned tasks to generate structured retrospective reports.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/sumilee-pcu/game2026 --skill retrospective-sumilee-pcu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/sumilee-pcu/game2026/tree/main/.claude/skills/retrospective
Command: npx skills add https://github.com/sumilee-pcu/game2026 --skill retrospective-sumilee-pcu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of inconsistent or forgotten project reviews by automating the analysis of sprint performance, velocity, and technical debt.

Core Features & Use Cases

  • Automated Metrics: Calculates completion rates, velocity trends, and bug counts by comparing planned tasks against git history.
  • Technical Debt Tracking: Monitors TODO, FIXME, and HACK counts to ensure code quality doesn't degrade over time.
  • Actionable Insights: Generates a structured retrospective document with clear action items, owners, and deadlines to improve future iterations.

Quick Start

Run the retrospective skill for the current sprint by typing the command retrospective sprint-12.

Frequently Asked Questions about retrospective

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

FAQPage Schema
How do I automate sprint retrospective analysis using git commit history?

Automate sprint retrospective analysis by correlating git commit history with planned task data to evaluate velocity trends, technical debt, and task completion accuracy, generating a structured report with actionable insights for continuous team improvement.

What is technical debt tracking and how does it monitor code quality during a sprint?

Technical debt tracking monitors code quality by counting TODO, FIXME, and HACK tags in the codebase across sprints. This ensures code quality doesn't degrade over time by highlighting accumulating debt in the retrospective analysis.

How do I calculate velocity trends and task completion rates for an agile milestone?

Calculate velocity trends and task completion rates by comparing planned sprint tasks against actual git commit history. This correlation evaluates performance accuracy and produces structured metrics for the retrospective report.

Can I generate actionable retrospective reports with assigned owners and deadlines?

Yes, you can generate structured retrospective reports featuring clear action items, designated owners, and specific deadlines. This facilitates continuous improvement through data-driven process optimization for future iterations.

Does retrospective analysis work without integrating external project management components?

Yes, retrospective analysis works independently without external dependencies or components. It analyzes sprint performance by directly correlating internal git commit history with planned task data to produce structured retrospective reports.

Why should I use automated sprint analysis instead of manual project reviews?

Automated sprint analysis solves the problem of inconsistent or forgotten manual project reviews by automatically calculating completion rates, velocity trends, and bug counts, ensuring continuous improvement through data-driven action items.