retro-engineer

Analyze Git repository activity into structured engineering retrospectives with action items.

2|1|Updated Jul 25, 2026
One-click install
npx skills add https://github.com/CODE-SAURABH/OpenSkills --skill retro-engineer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro-engineer
Source: https://github.com/CODE-SAURABH/OpenSkills/tree/main/retro-engineer
Command: npx skills add https://github.com/CODE-SAURABH/OpenSkills --skill retro-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill transforms scattered repository activity into structured engineering retrospectives, helping teams understand delivery patterns, test health, collaboration, and concrete improvement opportunities.

Core Features & Use Cases

  • Team Retrospectives: Analyze commits, pull requests, contributors, shipping streaks, velocity, test activity, and individual growth areas for a repository or sprint.
  • Global Retrospectives: Compare activity across repositories and AI-assisted tools to identify productivity trends, bus-factor risks, documentation debt, and security signals.
  • Structured Follow-Through: Produce consistent reports with wins, improvements, experiments, action items, definitions of done, cadence recommendations, and compact summaries for team communication.
  • Use Case: Run a weekly retrospective for a software repository to identify which features shipped, whether test health improved, where process risks exist, and which owners should take the next actions.

Quick Start

Ask the retro-engineer skill to run a weekly Team Retro for the current repository and save the completed report with prioritized action items.

Frequently Asked Questions about retro-engineer

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

FAQPage Schema
How do I generate an engineering retrospective from Git history?

To generate an engineering retrospective from Git history, the skill analyzes repository commits and pull requests to extract delivery patterns, test health, and collaboration metrics. It transforms this activity into a structured report with action items and owners.

Can I measure team velocity and test health using repository analytics?

Yes, you can measure team velocity and test health using repository analytics. The skill evaluates commit activity and test metrics to calculate shipping streaks and highlight individual growth areas for sprint-based team reviews.

How do I run a weekly sprint review for a software repository?

To run a weekly sprint review for a software repository, the skill detects your environment and time-window to compare metrics. It identifies shipped features, process risks, and documentation debt, then outputs cadence recommendations.

What is the best way to track developer productivity and action items across multiple repositories?

The best way to track developer productivity across multiple repositories is by running a global retrospective. The skill compares cross-project activity and AI tool usage to identify productivity trends, bus-factor risks, and security signals.

Does this approach require the GitHub CLI to detect organizational risks?

No, it does not strictly require the GitHub CLI to detect organizational risks, as it primarily uses Git history. However, GitHub CLI data is optional and provides additional pull request context for identifying bus-factor risks and security signals.

What is included in a structured engineering retrospective report?

A structured engineering retrospective report includes wins, improvements, experiments, and prioritized action items. It also features a definition-of-done checklist, assigned owners with due dates, and a compact summary for team communication.