avad-retro

Analyze git history to generate weekly engineering retrospective reports.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/agwacom/avadbot --skill avad-retro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: avad-retro
Source: https://github.com/agwacom/avadbot/tree/main/skills/avad-retro
Command: npx skills add https://github.com/agwacom/avadbot --skill avad-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives require collecting and synthesizing git history, contributor activity, and code quality signals across potentially multiple repositories. This Skill automates that process, turning raw data into a structured narrative you can review with your team.

Core Features & Use Cases

  • Per-repo and cross-repo commit analysis with time-windowing and local-time alignment.
  • Per-author stats, hotspot detection, and backlog signals (TODOS.md) when available.
  • Optional bot-review-history signals and test-health indicators to enrich the retro narrative.

Quick Start

Run the /avad-retro command to generate the weekly retrospective for the default 7-day window.

Frequently Asked Questions about avad-retro

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

FAQPage Schema
How do I automate weekly engineering retrospectives from git history?

Git commit analysis for retrospectives identifies engineering activity by parsing commit history, calculating insertions, deletions, and file churn, then summarizing per-author stats and hotspots into a data-rich narrative.

Can I run a git commit analysis retro across multiple repositories?

Yes, this Skill handles both single-repo and multi-repo contexts. It applies cross-repo commit analysis with time-windowing and local-time alignment to synthesize contributor activity across multiple repositories.

What git commit metrics are included in an automated team retro?

Automated retrospectives include per-contributor stats, insertions, deletions, test activity, file churn, hotspot detection, and backlog signals. Optional bot-review history and TODOS.md files further enrich the retro narrative.

How do I generate a weekly retrospective for a custom time window?

Run the /avad-retro command to generate a retrospective for the default 7-day window. The Skill applies time-windowing and local-time alignment to parse commits within your specified period.

Does the retro analysis require a TODOS.md file or bot-review history?

No, TODOS.md and bot-review history are optional signals that enrich the retro narrative. The core analysis requires parsing git commits to populate insertions, deletions, test activity, and file churn.