skills.rest
pcaokhai
pcaokhaiCOMMUNITY
Explore all skills by this author →
GitHub

retro

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

Updated Mar 24, 2026
Search Tags:#git#metrics#engineering#team#summaries#retro
One-click install
npx skills add https://github.com/pcaokhai/gradion-response-report-api --skill retro-pcaokhai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/pcaokhai/gradion-response-report-api/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/pcaokhai/gradion-response-report-api --skill retro-pcaokhai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives help teams identify actionable improvements by distilling a week's code activity, patterns, and outcomes into a structured reflection.

Core Features & Use Cases

  • Analyze commit history, work patterns, and code quality metrics with per-person praise and growth recommendations.
  • Preserve a persistent history of retros through time, enabling trend analysis and focused follow-ups.
  • Use during sprint reviews or planning to surface concrete next steps and focus areas for the coming cycle.

Quick Start

Ask Claude to generate a weekly retro for the current repository from the last 7 days and present a concise, actionable summary.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate a weekly engineering retrospective from git commit history?▼

To generate a weekly engineering retrospective, ask Claude to analyze the last 7 days of git commit history, work patterns, and code quality metrics to produce a concise, actionable summary for your team.

What metrics are included in a code activity retrospective?▼

A code activity retrospective evaluates commit history, work patterns, and code quality metrics, highlighting per-person praise and growth recommendations to guide engineering improvements.

Can I track engineering team progress and trends over multiple sprints?▼

Yes, you can track engineering team progress because the retro preserves a persistent history of retros through time, enabling trend analysis and focused follow-ups for continuous improvement.

When should I run a sprint review retrospective for my engineering team?▼

Run a sprint review retrospective when reviewing weekly progress or planning sprints; it proactively suggests concrete next steps and focus areas for the coming cycle at sprint end.

Does the retro analysis provide individual feedback for engineering team members?▼

Yes, the retro analysis provides individual feedback by highlighting per-person praise and growth recommendations based on each team member's code activity and work patterns during the week.

What's the best way to surface actionable insights from a team's code activity?▼

The best way to surface actionable insights is to distill a week's code activity, patterns, and outcomes into a structured retrospective reflection that identifies concrete improvements and focus areas.

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
serejarisserejaris
215

cc-analytics

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

Community
Intermediate
mejangomejango

sarif-parsing

Parse SARIF 2.1.0 files to extract and deduplicate findings.

Community
Intermediate
greencmgreencm
1

retro

Analyze commit history and work patterns to generate engineering retro summaries.

Community
Intermediate