skills.rest
hamzaPixl
hamzaPixlCOMMUNITY
Explore all skills by this author →
Website𝕏@pixlHamzaGitHub

retro

Generate engineering retrospective reports from git repository history.

2|Updated Mar 16, 2026
Search Tags:#git#analysis#retrospective#velocity#code churn#contributors
One-click install
npx skills add https://github.com/hamzaPixl/pixl-ai --skill retro-hamzapixl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/hamzaPixl/pixl-ai/tree/main/packages/crew/skills/retro
Command: npx skills add https://github.com/hamzaPixl/pixl-ai --skill retro-hamzapixl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Software teams often lack a quick, data‑driven view of recent development activity, making it hard to assess shipping velocity, code churn, hotspots, and individual contributions.

Core Features & Use Cases

  • Time‑windowed retrospectives (24h, 7d, 14d, 30d) summarizing commits, PRs, and lines changed.
  • Hotspot detection highlighting files or directories with high churn.
  • Contributor breakdown showing per‑author commit counts, net lines, and focus areas.
  • Compare mode contrasting the current period with the previous one to spot trends.
    Typical use case: a sprint review meeting where the team needs a concise report of what shipped and where technical debt may be accumulating.

Quick Start

Ask the retro skill for a 7‑day engineering retrospective of the current repository.

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

To generate an engineering retrospective from git history, use the retro skill to analyze time-windowed commit data, producing a report on code churn, velocity, hotspots, and contributor metrics for your repository.

Can I compare code churn and velocity between different sprint periods?▼

Yes, you can compare code churn and velocity between periods using the compare mode, which contrasts the current time window with the previous one to spot emerging trends in contributor activity and hotspots.

What git metrics are included in a time-windowed retrospective report?▼

A time-windowed retrospective report includes git metrics such as commit counts, lines changed, PR data, code churn, velocity trends, hotspot detection, and per-author contributor breakdowns.

Do I need GitHub CLI to analyze repository contributions and hotspots?▼

You do not need GitHub CLI to analyze basic repository contributions and hotspots; git CLI access is required, while GitHub CLI is optional and used to gather additional PR data for the retrospective.

How does hotspot detection identify technical debt in a codebase?▼

Hotspot detection identifies technical debt by analyzing git history to highlight specific files or directories with high code churn, indicating areas of frequent changes and potential instability.

What is the best way to summarize recent development activity for a sprint review?▼

The best way to summarize recent development activity for a sprint review is generating a 7-day or 30-day retrospective, which extracts commit, churn, and contributor data to concisely report what shipped.

Related Skills

Explore More Software Engineering Skills→
KrismithReddy12KrismithReddy12

gstack-openclaw-retro

Analyze git commit history to generate engineering retrospectives and team performance metrics.

Community
Advanced
aiunlocked1412aiunlocked1412
14

agile-coach

Generate sprint planning packages with capacity calculations and ceremony scripts.

Community
Intermediate
BerryKuipersBerryKuipers
7

fetch-github-issue-analysis

Fetch GitHub issue data and AI analysis comments into structured JSON.

Community
Intermediate
MissTullyMissTully

gstack-openclaw-retro

Analyze Git history and commit metadata to generate weekly engineering retrospectives.

Community
Advanced