skills.rest
chiruu12
chiruu12COMMUNITY
Explore all skills by this author →
WebsiteGitHub

retro

Analyze commit history, work patterns, and code quality metrics for engineering retrospectives.

1|Updated May 25, 2026
Search Tags:#code quality#commit history#team analysis#retro#engineering retrospective
One-click install
npx skills add https://github.com/chiruu12/nudge --skill retro-chiruu12
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/chiruu12/nudge/tree/main/.agents/skills/gstack-retro
Command: npx skills add https://github.com/chiruu12/nudge --skill retro-chiruu12

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, code analysis tools, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the analysis of commit history, work patterns, and code quality metrics for weekly engineering retrospectives, providing persistent history and trend tracking.

Core Features & Use Cases

  • Commit History Analysis: Reviews commit history to understand work patterns and contributions.
  • Code Quality Metrics: Evaluates code quality using various metrics and provides insights.
  • Team Awareness: Breaks down contributions by individual team members with praise and areas for growth.
  • Use Case: Ideal for answering questions like "weekly retro", "what did we ship", or "engineering retrospective" by providing a comprehensive analysis at the end of a work week or sprint.

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 automate commit history analysis for an engineering retrospective?▼

Automating commit history analysis for an engineering retrospective requires parsing git logs to evaluate work patterns and code quality metrics. This Skill generates a comprehensive report summarizing team contributions and areas for improvement.

What code quality metrics can I extract from commit history for team analysis?▼

Code quality metrics extracted from commit history for team analysis include work patterns and individual contributions. The Skill evaluates these metrics to provide insights, highlighting specific team member contributions with praise and areas for growth.

Can I use this Skill to track what my team shipped during a weekly sprint?▼

Yes, you can use this Skill to track what your team shipped during a weekly sprint. It analyzes commit history and code quality to answer questions like "what did we ship" by providing a comprehensive engineering retrospective report.

Do I need git and code analysis tools to generate a weekly engineering retrospective?▼

Yes, you need git and code analysis tools to generate a weekly engineering retrospective. The Skill requires access to version control systems and code analysis utilities to automate the extraction of work patterns and quality metrics.

What is the best way to analyze individual developer contributions for a retro?▼

The best way to analyze individual developer contributions for a retro is by automating commit history parsing to map work patterns. This Skill breaks down contributions by team members, offering targeted insights for growth and praise.

Related Skills

Explore More Software Engineering Skills→
lis186lis186
46

history-analyzer

Analyze git history to identify hotspots, coupling, and knowledge distribution.

Community
Basic
AlejandroFiginiAlejandroFigini

retro

Analyze commit history and code quality trends to generate weekly retrospective summaries.

Community
Intermediate
alinaqialinaqi
705

commit-hygiene

Enforce atomic commits and small pull requests with file and line count thresholds.

Community
Intermediate
josephneumannjosephneumann
4

retro

Analyze Git commit history to generate engineering retrospective reports.

Community
Advanced