skills.rest
Yaugourt
YaugourtCOMMUNITY
Explore all skills by this author →
𝕏@YaugourtGitHub

retro

Generate engineering retrospectives from commit history and contributor data over a specified window.

2|2|Updated Dec 1, 2024
Search Tags:#engineering#growth#code-quality#commit-history#retro#praise
One-click install
npx skills add https://github.com/Yaugourt/LiquidTerminal_Back --skill retro-yaugourt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/Yaugourt/LiquidTerminal_Back/tree/main/.agents/skills/gstack/retro
Command: npx skills add https://github.com/Yaugourt/LiquidTerminal_Back --skill retro-yaugourt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams capture and summarize weekly engineering activity from commit data to surface praise, growth opportunities, and actionable feedback.

Core Features & Use Cases

  • Per-person praise and growth insights derived from commit histories.
  • Time-window based retrospectives (default last 7 days) that scale to cross-project uses with Global Retro flow.
  • Generates a clear narrative for developers and leaders to spot strengths, gaps, and priorities.

Quick Start

Type /retro to generate the weekly retrospective for the last 7 days.

Frequently Asked Questions about retro

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

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

To generate a team engineering retrospective from commit history, type /retro to analyze the last 7 days of contributor activity and code-quality signals. It outputs structured metrics, per-author summaries, and actionable insights.

What is a commit history based engineering retrospective?▼

A commit history based engineering retrospective analyzes repository commit data within a specific time window to surface per-person praise and growth areas, producing an overall narrative suitable for engineers and leaders.

Can I scope an engineering retrospective to a custom time window?▼

Yes, you can scope an engineering retrospective to a custom time window. The default scope is the last 7 days, but it supports user-specified time windows and can scale to cross-project uses with a Global Retro flow.

How do code-quality signals get used in weekly engineering retros?▼

Code-quality signals from commit data are analyzed during weekly engineering retros to identify team strengths and gaps. This process surfaces per-person praise and growth opportunities, generating actionable feedback for developers and leaders.

Do I need additional tools to produce per-author summaries from repository commits?▼

No additional tools are required to produce per-author summaries from repository commits. The process requires only access to the repository's commit data within the specified time window to generate structured metrics and actionable insights.

What is the best way to summarize weekly engineering activity for team leaders?▼

The best way to summarize weekly engineering activity for team leaders is to analyze contributor activity and code-quality signals from commit data, which generates a clear narrative to spot strengths, gaps, and priorities.

Related Skills

Explore More Software Engineering Skills→
jerrywu001jerrywu001
6

retro

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

Community
Advanced
ligianehualigianehua

retro

Analyze git commit history to generate a team-aware weekly retrospective.

Community
Advanced
lemiglemig

retro

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

Community
Advanced
louisfghbvclouisfghbvc
4

retro

Analyze commit history and code quality metrics to summarize engineering activity.

Community
Advanced