skills.rest
yckkkk
yckkkkCOMMUNITY
Explore all skills by this author →
GitHub

retro

Analyze commit history and code quality metrics to generate weekly retrospective summaries.

1|Updated May 6, 2026
Search Tags:#automation#engineering#growth#code-quality#commit-history#retro#team-feedback
One-click install
npx skills add https://github.com/yckkkk/reo --skill retro-yckkkk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/yckkkk/reo/tree/main/.agents/skills/retro
Command: npx skills add https://github.com/yckkkk/reo --skill retro-yckkkk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives tend to stagnate without structured analysis of history and growth opportunities. This Skill analyzes commit history, work patterns, and code quality metrics to surface actionable insights and maintain persistent retrospectives across sprints.

Core Features & Use Cases

  • Per-person contributions breakdown with praise and growth areas for each sprint.
  • Persistent history and trend tracking across weeks, with summaries you can reference in future planning.
  • Team-aware analysis of commits, reviews, and quality metrics to guide process improvements.
  • Use cases include end-of-week retros, sprint reviews, and post-release reflections to identify bottlenecks and opportunities.

Quick Start

To start, say weekly retro to generate a retrospective from the latest sprint data.

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

Automate weekly engineering retrospectives by analyzing commit history and code quality metrics to compute per-person contributions. The system generates a structured summary with actionable recommendations and growth areas for each sprint.

What is the best way to track per-person code quality trends across sprints?▼

Track per-person code quality trends by collecting commit history and computing individual metrics across weeks. This produces persistent trend tracking with praise and growth areas to reference in future sprint planning.

Can I use automated retrospectives for sprint reviews and post-release reflections?▼

Automated retrospectives support sprint reviews and post-release reflections by surfacing team-aware analysis of commits and reviews. They identify bottlenecks and opportunities to guide process improvements at week close.

Does automated team feedback analysis work without external dependencies?▼

Automated team feedback analysis works without external dependencies to collect engineering activity history. It computes per-person metrics internally to output structured summaries and actionable growth-oriented insights.

How do I generate a retrospective from the latest sprint data?▼

Generate a retrospective from the latest sprint data by triggering the analysis on engineering activity. It automatically collects history, computes metrics, and outputs a structured summary with actionable recommendations.

Related Skills

Explore More Software Engineering Skills→
tblakex01tblakex01
1

gstack-openclaw-retro

Analyze commit history to generate structured weekly engineering retrospectives.

Community
Advanced
ivegamsftivegamsft

sprint-management

Provide templates for sprint planning, retrospectives, and backlog refinement.

Community
Advanced
koderoverkoderover
7

sonar

Retrieve and analyze SonarQube code quality metrics and quality gate statuses.

Official
Intermediate
singhianand23045singhianand23045

retro

Generate weekly engineering retrospectives from Git data and test results.

Community
Intermediate