skills.rest
psyche911
psyche911COMMUNITY
Explore all skills by this author →
GitHub

retro

Aggregate Git history and commit metadata into structured JSON retrospectives.

Updated Jan 18, 2026
Search Tags:#git#analysis#metrics#engineering#team#retro
One-click install
npx skills add https://github.com/psyche911/investor-council-app --skill retro-psyche911
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/psyche911/investor-council-app/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/psyche911/investor-council-app --skill retro-psyche911

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives help teams reflect on their work, surface patterns in commits, and identify growth areas. The skill analyzes commit history, work patterns, and code quality metrics with a persistent history to enable team-level learning and per-person praise.

Core Features & Use Cases

  • Generates per-author insights and a trend-tracked narrative for engineering teams.
  • Produces structured data outputs suitable for post-iteration reviews and leadership reporting.
  • Use Case: imagine your team completed a sprint; this retro aggregates the windowed activity to highlight focus areas and opportunities.

Quick Start

Generate a weekly retro for the default 7-day window, or specify a custom window to tailor the analysis.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I automate weekly engineering retrospectives from Git history?▼

Automate weekly engineering retrospectives by analyzing Git commits, authors, and file changes within a defined time window to identify team collaboration patterns and produce actionable insights.

Can I generate per-author metrics for a custom sprint window?▼

Yes, you can generate per-author metrics by specifying a custom time window. The analysis aggregates commit metadata to provide per-person breakdowns suitable for individual praise and growth tracking.

How does session detection work for engineering team commit analysis?▼

Session detection for engineering team commit analysis works by aggregating Git history and file changes within the specified time window, identifying work patterns and focus areas across authors.

Does this Git analysis tool output structured data for leadership reporting?▼

Yes, this Git analysis tool outputs structured JSON data containing commit metrics and per-author insights, making it suitable for post-iteration reviews, historical comparisons, and leadership reporting.

What is the best way to track engineering team collaboration patterns across sprints?▼

Track engineering team collaboration patterns across sprints by using persistent history with structured JSON outputs, enabling trend-tracked narratives that surface work patterns and identify growth areas over time.

Can I use this retrospective tool for solo contributors and cross-functional projects?▼

Yes, you can use this retrospective tool for solo contributors and cross-functional projects. It analyzes commit history and work patterns within any defined time window to highlight focus areas.

Related Skills

Explore More Software Engineering Skills→
Intension-usIntension-us

retro

Analyze Git commit history and code quality metrics to generate weekly engineering retrospectives.

Official
Advanced
serejarisserejaris
215

cc-analytics

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

Community
Intermediate
a29paula29paul
1

retro

Generate weekly engineering retrospectives from git commit history and code quality metrics.

Community
Advanced
yocxy2yocxy2

gstack-openclaw-retro

Analyze git commit history to generate engineering retrospectives.

Community
Advanced