skills.rest
26mitch26
26mitch26COMMUNITY
Explore all skills by this author →
GitHub

retro

Analyze commit history and code quality metrics for weekly retrospectives.

Updated Jun 11, 2026
Search Tags:#code quality#retrospective#team collaboration#commit history#work patterns
One-click install
npx skills add https://github.com/26mitch26/ai-mall --skill retro-26mitch26
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/26mitch26/ai-mall/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/26mitch26/ai-mall --skill retro-26mitch26

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, grep, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps teams to conduct a weekly engineering retrospective, tracking progress, identifying learnings, and discussing past work.

Core Features & Use Cases

  • Commit History Analysis: Analyzes commit history to understand work patterns and code quality.
  • Trend Tracking: Tracks trends in contributions and code quality over time.
  • Team Awareness: Breaks down contributions by individuals, providing praise and areas for growth.
  • Use Case: Use this Skill at the end of a work week or sprint to discuss what was shipped, what went well, and what could be improved.

Quick Start

Use the retro skill to start a weekly engineering retrospective for your project.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I run a weekly engineering retrospective using git commit history?▼

To run a weekly engineering retrospective, this Skill analyzes git commit history, work patterns, and code quality metrics from your project repository to track progress and structure learnings. It provides a structured format for discussing what was shipped and what could be improved.

What is a code quality retrospective and how does it track team work patterns?▼

A code quality retrospective analyzes project repositories to track trends in contributions and work patterns over time. It breaks down individual contributions to provide praise and identify areas for growth during weekly team reviews.

Do I need git and grep installed to analyze commit history for a team retrospective?▼

Yes, you need both git and grep installed. The Skill requires access to your project repository and relies on these dependencies to analyze commit history, extract work patterns, and calculate code quality metrics for the retrospective.

Can I track individual developer contributions and code quality trends over time?▼

Yes, you can track individual developer contributions and code quality trends over time. The retrospective Skill breaks down contributions by individuals to highlight specific praise and areas for growth based on commit history analysis.

What's the best way to discuss what went well and what could be improved after a sprint?▼

The best way to discuss sprint outcomes is using a structured retrospective format that analyzes commit history and code quality metrics. This provides data-backed insights into what went well, what was shipped, and what can be improved.

Related Skills

Explore More Software Engineering Skills→
samjhechtsamjhecht
4

initialize-governance

Generate Constitution, Roadmap, and process documentation templates for project governance.

Community
Advanced
abhishekchoudhariabhishekchoudhari
1

retro

Facilitate structured sprint retrospectives and generate prioritized action items.

Community
Intermediate
RxFitRxFit

retro

Analyze Git commit history to generate weekly engineering retrospectives.

Community
Advanced
serejarisserejaris
215

cc-analytics

Analyze Claude Code history and Git data into weekly HTML reports.

Community
Intermediate