skills.rest
nicholaslocascio
nicholaslocascioCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

retro

Analyze commit history and author contributions to generate engineering retrospective summaries.

2|Updated Mar 20, 2026
Search Tags:#git#analysis#metrics#quality#team#retro
One-click install
npx skills add https://github.com/nicholaslocascio/x-claw-studio --skill retro-nicholaslocascio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/nicholaslocascio/x-claw-studio/tree/main/skills/gstack/retro
Command: npx skills add https://github.com/nicholaslocascio/x-claw-studio --skill retro-nicholaslocascio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives bridge the gap between raw code activity and actionable team improvements. This Skill analyzes commit history, work patterns, and code quality metrics to surface a persistent history of contributions and trends.

Core Features & Use Cases

  • Aggregates commits, insertions, deletions, and file changes across a configurable time window to reveal activity patterns.
  • Produces per-author contributions, focus signals, and a highlight of the ship of the week to inform planning.
  • Generates a narrative and a shareable summary that helps teams reflect and plan improvements.

Quick Start

Run the retro skill to generate this week's engineering retrospective for the current repository.

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

To generate an engineering retrospective from git commit history, analyze commit activity, author contributions, and file changes within a defined time window to produce a narrative summary and a machine-friendly JSON snapshot.

Can I summarize weekly team engineering activity from a git repository?▼

You can summarize weekly team engineering activity by analyzing commit history on the repository's default branch, aligning timestamps to Pacific time, and highlighting per-author contributions and the ship of the week.

Does the git retrospective analysis output a structured data format?▼

The git retrospective analysis outputs a structured, human-readable narrative summary suitable for team planning alongside a machine-friendly JSON snapshot capturing the engineering activity metrics.

What git branch configuration is needed for analyzing commit metrics?▼

Analyzing commit metrics requires using the repository's default branch via origin/<default> and aligning all commit timestamps to Pacific time to ensure accurate activity window aggregation.

How do I identify focus signals and work patterns from repository commits?▼

Identify focus signals and work patterns by applying commit history analysis across software repositories, which surfaces per-author contributions and activity patterns suitable for team planning and post-week sharing.

Related Skills

Explore More Software Engineering Skills→
NagyViktNagyVikt
2

auto-publish-after-plan

Stage, commit, and push verified changes to non-default Git branches with conventional messages.

Community
Intermediate
vikingokftvikingokft

recipe-email-drive-link

Generate a Google Drive shareable link and email it with a custom message.

Official
Intermediate
ManzuetiManzueti

cyberdart-openclaw-retro

Analyze commit history, code quality metrics, and PR metrics for engineering retrospectives.

Community
Advanced
geoffreywoogeoffreywoo

retro

Generates weekly engineering retrospective reports from Git commit history and per-author statistics.

Community
Advanced