skills.rest
yibeichan
yibeichanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

retro

Generate weekly engineering retrospectives from Git commit history and metrics.

1|Updated Mar 27, 2026
Search Tags:#code quality#test coverage#commit history#trend tracking#engineering retrospective#team contributions#git analytics
One-click install
npx skills add https://github.com/yibeichan/schist --skill retro-yibeichan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/yibeichan/schist/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/yibeichan/schist --skill retro-yibeichan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams stop losing context between weeks by turning commit history into a clear, time-bounded retrospective that highlights shipping progress, patterns in how work was done, and where code quality can improve.

Core Features & Use Cases

  • Weekly engineering retrospective: Produces metrics (commits, LOC, test activity, sessions, hotspots) for a chosen window and formats them into a team-ready summary.
  • Team-aware contribution analysis: Identifies the user (from git config) and breaks down work by contributor, including praise and growth opportunities based on observed patterns.
  • Trend and accountability loop: Tracks backlog health (TODOS.md when present), session/streak progress, optional greptile signals, and records a JSON snapshot for week-over-week comparison.

Quick Start

Tell your agent to run /retro to generate a 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 weekly engineering retrospective from Git commit history?▼

To generate a weekly engineering retrospective from Git commit history, run the /retro command to analyze the default branch for the last 7 days. It computes commits, LOC, and test activity metrics, outputting a team-ready summary.

What is an engineering retrospective and how does tracking commit history help?▼

An engineering retrospective analyzes commit history to surface shipping progress, work patterns, and code quality trends. Tracking these metrics helps teams stop losing context between weeks and identifies specific areas for follow-up action.

Can I track individual team contributions and code quality signals from Git analytics?▼

Yes, you can track team contributions and code quality signals from Git analytics. The retrospective identifies users from git config, breaks down work by contributor, and highlights praise or growth opportunities based on observed work patterns.

How do I compare week-over-week engineering trends and backlog health?▼

You compare week-over-week engineering trends by recording a JSON snapshot of your retrospective metrics. The tool tracks backlog health from TODOS.md and session progress, allowing you to load previous snapshots for direct trend comparisons.

Do I need a specific branch or local analytics setup to analyze code quality trends?▼

You need commits from the repo default branch to analyze code quality trends. The process optionally uses local analytics and a TODOS.md file to detect sessions, track backlog health, and compute focus trends for follow-up actions.

Related Skills

Explore More Software Engineering Skills→
agwacomagwacom

avad-retro

Analyze git history to generate weekly engineering retrospective reports.

Official
Advanced
bhianerdbhianerd
1

retro

Analyze git commit history to generate weekly engineering retrospectives.

Community
Advanced
snewhousesnewhouse
6

retro

Convert git commit history into weekly engineering retrospective metrics.

Community
Advanced
GenEducationGenEducation

retro

Analyze git commit history to generate weekly engineering retrospectives.

Official
Advanced