retro

Analyze Git history to generate weekly retrospective reports.

4|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/AGMO-Inc/agmo-everywhere --skill retro-agmo-inc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/AGMO-Inc/agmo-everywhere/tree/main/skills/retro
Command: npx skills add https://github.com/AGMO-Inc/agmo-everywhere --skill retro-agmo-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill generates a weekly retrospective by analyzing a project's Git history, turning raw commit activity into a structured, narrative digest that informs team learning and improvement.

Core Features & Use Cases

  • Automated weekly retrospectives: synthesize commit data into a concise report with metrics (commits, files changed, lines added/deleted) and thematic insights.
  • Project-scoped analysis: works for a single repository and can target a specific period (default current week, with user-specified ranges like 지난주 or custom dates).
  • Vault integration: saves the retrospective to the Obsidian vault and updates project retrospectives indexes for traceability.

Quick Start

Request a weekly retro for your project and period.

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 retrospective from Git history?

Generating a weekly retrospective from Git history involves applying the skill to a specific project and time window. It collects commits via git log, computes totals like files changed and lines added, and saves the narrative digest to your Obsidian vault.

Can I analyze Git commits for a specific time period like last week?

You can analyze Git commits for a specific time period by applying the skill to your project with a specified range. It defaults to the current week but accepts overrides like '지난주' or custom dates to collect and compute commit totals accurately.

Does the retrospective tool require an Obsidian vault to save reports?

Yes, the retrospective tool saves generated reports directly to an Obsidian vault. It uses the archivist workflow to store the weekly digest and update project retrospectives indexes, ensuring your Git history analysis remains traceable.

What Git metrics are included in an automated weekly retrospective?

Automated weekly retrospectives include Git metrics like total commits, files changed, and lines added and deleted. The skill computes these totals from your git log to turn raw commit activity into a structured narrative digest.

What is the best way to turn raw Git commit activity into a structured digest?

The best way to turn raw Git commit activity into a structured digest is by running an automated retrospective. The skill processes your git log, computes commit totals, and synthesizes the data into a concise narrative report saved to your vault.