skills.rest
Mathews-Tom
Mathews-TomCOMMUNITY
Explore all skills by this author →
𝕏@tom_mathewsGitHub

engineering-retro

Analyze Git repositories to generate structured engineering retrospectives with commit metrics.

310|45|Updated Feb 22, 2026
Search Tags:#git#retrospective#monorepo#engineering#sessions#velocity#commit-analysis
One-click install
npx skills add https://github.com/Mathews-Tom/armory --skill engineering-retro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: engineering-retro
Source: https://github.com/Mathews-Tom/armory/tree/main/skills/engineering-retro
Command: npx skills add https://github.com/Mathews-Tom/armory --skill engineering-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes a Git repository to produce a structured engineering retrospective over a configurable time window, helping teams review recent velocity and delivery patterns without manual compilation.

Core Features & Use Cases

  • Automated metrics: Computes commits, unique contributors, files changed, and lines added/removed within the selected window.
  • Session and hotspot analysis: Groups work into sessions and identifies hotspots to guide improvements.
  • Outputs for comparisons: Provides per-author breakdowns and a JSON snapshot suitable for week-over-week analysis.

Quick Start

Run the retrospective for the default 7-day window using the /engineering-retro command, with an optional path scope as needed.

Frequently Asked Questions about engineering-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 history, you can run the /engineering-retro command to automatically analyze commits, contributors, and code velocity over a configurable time window.

Can I scope a git retrospective analysis to a specific subdirectory in a monorepo?▼

Yes, git retrospective analysis supports monorepos by allowing you to specify an optional path scope, restricting the commit analysis and metrics generation to a targeted subdirectory.

What metrics are included in an automated git repository retrospective?▼

An automated git repository retrospective includes metrics such as total commits, unique contributors, files changed, lines added and removed, work sessions, per-author breakdowns, and identified hotspot files.

How do I track engineering velocity trends week over week using git data?▼

You can track engineering velocity trends by using the JSON snapshot output generated from the git analysis, which provides structured historical data for direct week-over-week performance comparisons.

Does this git retrospective tool require any external integrations or dependencies?▼

No external dependencies are required to run the git retrospective, as it directly analyzes the local Git repository history to compute engineering velocity and delivery patterns.

How are coding sessions identified during git commit analysis?▼

During git commit analysis, coding sessions are identified by grouping chronological commits into clustered work periods, helping teams review development focus and workflow patterns without manual compilation.

Related Skills

Explore More Software Engineering Skills→
alangebalangeb

git-advanced

Perform Git bisecting, cherry-picking, and log analysis operations locally.

Community
Advanced
EvolutionAPIEvolutionAPI
520

prod-trends

Compares weekly community, GitHub, and financial metrics to detect patterns and risks.

Official
Advanced
xinbenlvxinbenlv
8

codereview-architect

Analyze blast radius and trace dependencies across codebases to enforce architectural boundaries.

Community
Advanced
jholhewresjholhewres
3

sprint-report

Generates sprint reports by analyzing Git history and issue tracker data.

Community
Intermediate