skills.rest
fray-cloud
fray-cloudCOMMUNITY
Explore all skills by this author →
GitHub

retro

Generate weekly engineering retrospectives from git commit history and metrics.

Updated Mar 23, 2026
Search Tags:#git#metrics#engineering#code-quality#sprint#retro#team-feedback
One-click install
npx skills add https://github.com/fray-cloud/coin --skill retro-fray-cloud
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/fray-cloud/coin/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/fray-cloud/coin --skill retro-fray-cloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives capture learnings from the past sprint or week by analyzing commit history, work patterns, and code quality metrics to surface actionable insights.

Core Features & Use Cases

  • Team-aware analysis of per-person contributions, praise, and growth opportunities.
  • Persistent history and trend tracking of engineering metrics across sprints.
  • Workflow-friendly retrospectives for sprint reviews, release retros, and post-mortems.

Quick Start

Run the retro with /retro to generate the last 7 days and append to the persistent history, or specify a different window like /retro 14d for a longer view.

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

Generate an engineering retrospective by analyzing git commit history, work patterns, and code quality metrics to surface actionable insights for your team. The output provides a readable narrative with per-person contributions and growth opportunities.

What is a data-driven sprint retrospective for engineering teams?▼

A data-driven sprint retrospective analyzes commit history and code quality metrics to surface actionable insights, per-person contributions, and trend tracking across sprints. It replaces manual reflection with persistent historical engineering metrics.

Can I run a retrospective for multiple repositories at once?▼

Yes, you can analyze work patterns and code quality metrics across one or multiple repositories. The retrospective surfaces trend insights and contributions from the entire team regardless of the repository boundaries.

How do I analyze code quality metrics for a 14-day sprint review?▼

Specify a custom window like 14d to analyze a longer period of git history and code quality metrics. The retrospective appends the results to a persistent history for ongoing trend tracking across sprints.

Does a git-based retrospective require access to the full repository history?▼

Yes, generating the retrospective requires access to git history and metrics to analyze commit patterns and code quality. This access enables the tool to surface accurate per-person contributions and trend insights.

What is the best way to track engineering team contributions over time?▼

Use a retrospective tool that persists a historical record of engineering metrics and commit analysis across sprints. This approach surfaces trend insights and tracks per-person contributions and growth opportunities over time.

Related Skills

Explore More Software Engineering Skills→
kk20300113-pngkk20300113-png

retro

Analyze git commit history to generate weekly engineering retrospective reports.

Community
Advanced
phurynphuryn
25.0k

retro

Facilitate structured sprint retrospectives and generate prioritized action items with owners and deadlines.

Community
Intermediate
GTC6244GTC6244

retro

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

Community
Advanced
HouseofmvpsHouseofmvps
115

retro

Analyze git repository history to generate structured sprint retrospective reports.

Community
Intermediate