skills.rest
mostafasudo
mostafasudoCOMMUNITY
Explore all skills by this author →
Website𝕏@mostafasudoGitHub

retro

Analyze Git commit history to generate weekly engineering retrospective reports.

3|Updated Oct 12, 2025
Search Tags:#project management#code review#team collaboration#commit analysis#retro
One-click install
npx skills add https://github.com/mostafasudo/warpy --skill retro-mostafasudo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/mostafasudo/warpy/tree/main/.codex/skills/gstack/retro
Command: npx skills add https://github.com/mostafasudo/warpy --skill retro-mostafasudo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, read, write, glob, askuserquestion, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps teams review their progress, identify areas for improvement, and plan future tasks with a comprehensive weekly engineering retrospective.

Core Features & Use Cases

  • Commit History Analysis: Automatically analyze commit history to understand work patterns and code quality.
  • Trend Tracking: Monitor team performance over time with persistent history and trend tracking.
  • Personalized Insights: Break down contributions per team member with praise and growth areas.
  • Use Case: Use this Skill at the end of a work week or sprint to review what was shipped, discuss challenges, and plan upcoming tasks.

Quick Start

Run the 'retro' skill to generate a weekly engineering retrospective report.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I analyze commit history for a weekly engineering retrospective?▼

To analyze commit history for an engineering retrospective, run the 'retro' skill to automatically extract work patterns, track performance trends, and generate a comprehensive weekly report directly from your project's filesystem.

What is the best way to track team progress and code review contributions over time?▼

Tracking team progress and code review contributions is best handled by persistent history analysis, which monitors performance trends over time and breaks down individual contributions to highlight praise and growth areas.

Do I need Git and filesystem access to generate a project retrospective report?▼

Yes, you need Git and filesystem access to generate a retrospective report, as the skill requires direct read access to your project history and local codebase to extract personalized team insights.

Can I use commit analysis to identify areas for improvement after a sprint?▼

Yes, you can use commit analysis to identify areas for improvement after a sprint by reviewing what was shipped, discussing challenges, and breaking down contributions per team member to highlight specific growth areas.

How does commit analysis work for team collaboration insights?▼

Commit analysis for team collaboration works by parsing Git history via Bash and Read tools to extract work patterns, evaluate code quality, and output persistent records that track team performance trends over time.

Related Skills

Explore More Software Engineering Skills→
26mitch2626mitch26

gstack-openclaw-retro

Analyze Git commit history to generate engineering retrospective reports.

Community
Advanced
ClyptAIClyptAI

retro

Analyze commit history and code quality to generate team-aware retrospective summaries.

Official
Advanced
bitwardenbitwarden
129

retrospecting

Generate structured retrospective reports from Claude Code session data.

Official
Intermediate
BaGyun0107BaGyun0107

retro

Analyze commit history and work patterns for engineering retrospectives.

Community
Intermediate