retro

Aggregates log.md and git history to generate period-based retrospective reports.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/samurano/ai-brain --skill retro-samurano
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/samurano/ai-brain/tree/main/.agents/skills/retro
Command: npx skills add https://github.com/samurano/ai-brain --skill retro-samurano

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes scripts (resource) components.

What problem does it solve?

Provides a structured retrospective by pairing log.md data with git history to reveal what was actually completed, where bottlenecks occurred, and which patterns repeat over a period.

Core Features & Use Cases

  • Combines log-based progress with commit history to deliver an objective project view for a defined period.
  • Identifies completed work, blockers, and recurring issues to guide planning for the next period.
  • Suitable for monthly reviews of a single project or overall status across the ai-brain repository.

Quick Start

Run a retrospective for a selected project and period by aggregating log.md and git history

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate a project retrospective from git history and log files?

Generate a project retrospective by aggregating log.md entries with git commit history to reveal completed work, blockers, and recurring patterns over a defined period. This pairs log-based progress with commit history to provide an objective project view.

Why combine git commit history with log.md for period-based reviews?

Combining git statistics with log.md data pairs objective commit history with progress notes to identify bottlenecks and recurring issues. This reveals what was actually completed versus planned work for a defined period.

Do I need git installed to run retrospectives on project logs?

Yes, git is required as a dependency to run the retrospective data collection script. The script executes git commands to gather statistics, which are then aggregated with log.md, decisions.md, and lessons.md data for analysis.

What is the best way to track recurring blockers and decisions for monthly project reviews?

Track recurring blockers and decisions by running a retrospective that reads decisions.md and lessons.md alongside git history and log.md. This surfaces repeating patterns and past decisions to guide planning for the next period.

Can I use this retrospective approach for a single project or across the entire repository?

You can run retrospectives for either a single project or across the entire repository for overall status analysis. The tool applies period-based review logic to analyze completed work, blockers, and recurring patterns at either scope.