retro

Analyze git history, issues, and session logs to generate structured retrospectives.

Updated Jun 21, 2026
One-click install
npx skills add https://github.com/apexradius/agentic-os --skill retro-apexradius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/apexradius/agentic-os/tree/main/skills/retro
Command: npx skills add https://github.com/apexradius/agentic-os --skill retro-apexradius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of conducting project retrospectives by analyzing git history, issues, and session logs, providing a structured review of what went well, what didn't, and actionable improvements.

Core Features & Use Cases

  • Git History Analysis: Reviews commits, branches, and tags to assess project progress.
  • Issue Tracking Integration: Considers open and closed issues to evaluate project planning and execution.
  • Session Log Review: Examines session summaries and progress documents for insights.
  • Framework-Based Analysis: Utilizes the "Start/Stop/Continue" framework for retrospective activities.
  • Use Case: Ideal for post-project phase reviews or as a standalone tool to enhance project management practices.

Quick Start

Run the retro skill on your project by executing 'retro [project-or-timeframe]' after completing a phase.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I automate a project retrospective using git history and issue tracking data?

Automating a project retrospective involves analyzing git commit history, issue tracking data, and session logs to evaluate project outcomes. This process structures the review using the Start/Stop/Continue framework to suggest actionable improvements.

What is the Start/Stop/Continue framework for project reviews?

The Start/Stop/Continue framework is a retrospective activity structure that categorizes project insights into actions to start doing, stop doing, and continue doing. It evaluates session logs and issue tracking data to generate actionable improvements.

Do I need a connected repository and issue tracking system to generate retrospective insights?

Yes, conducting an automated project retrospective requires access to the project repository and issue tracking system. These data sources provide the commit history, branch tags, and issue statuses needed to assess progress and execution.

What's the best way to review project progress after completing a development phase?

The best way to review project progress is executing a retrospective command on a specific project or timeframe. This analyzes git branches, tags, and closed issues to evaluate planning and execution, delivering structured insights for phase reviews.

Can I use session logs and progress documents to identify what went wrong in a project?

Yes, session log review examines session summaries and progress documents to identify project issues. Combined with issue tracking integration and git history analysis, it highlights what did not go well and suggests actionable improvements.