skills.rest
rmarino550
rmarino550COMMUNITY
Explore all skills by this author →
GitHub

retro

Generate engineering retrospective reports from commit history and code quality metrics.

Updated Mar 20, 2026
Search Tags:#code quality#retrospective#commit history#engineering workflow#team analytics
One-click install
npx skills add https://github.com/rmarino550/gstack --skill retro-rmarino550
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/rmarino550/gstack/tree/main/retro
Command: npx skills add https://github.com/rmarino550/gstack --skill retro-rmarino550

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of conducting weekly engineering retrospectives, providing detailed analytics on commit history, work patterns, and code quality metrics.

Core Features & Use Cases

  • Commit History Analysis: Analyzes commit history to track contributions, work patterns, and code quality.
  • Team Awareness: Breaks down contributions by individual team members with praise and growth opportunities.
  • Automated Reporting: Generates a comprehensive report that can be used for team discussions and improvement planning.

Quick Start

Run the /retro command 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 weekly engineering retrospectives using commit history?▼

You can automate engineering retrospectives by analyzing commit history, work patterns, and code quality metrics to generate a comprehensive report. This process tracks team progress and identifies areas for improvement.

Can I track individual code quality metrics and team contributions for a retrospective?▼

Yes, team analytics breakdown individual contributions using commit history, highlighting both praise and growth opportunities. This allows team leaders to track specific code quality metrics and work patterns for each member.

What do I need to generate an automated engineering workflow retrospective report?▼

You need access to the repository's commit history and user configuration. Once configured, running the /retro command analyzes work patterns and generates the retrospective report for team discussions.

How does analyzing commit history improve team awareness and engineering workflow?▼

Analyzing commit history improves team awareness by tracking individual contributions and code quality metrics. It identifies work patterns and growth opportunities, providing data to plan engineering workflow improvements.

What is the best way to run a code quality retrospective for my engineering team?▼

The best way is to automate the retrospective using commit history analysis. This provides detailed team analytics on code quality metrics and work patterns, generating a comprehensive report for improvement planning.

Related Skills

Explore More Software Engineering Skills→
256javy256javy

gstack-openclaw-retro

Extract commit history and author data into a structured weekly retro.

Community
Advanced
AllanYiinAllanYiin
2

document-workflows

Automate document creation, editing, and export across Markdown, Word, and PDF formats.

Community
Advanced
NoobyGainsNoobyGains
78

quality-enforcement

Enforce code quality standards across pre-commit, pre-merge, and CI pipeline stages.

Community
Advanced
maltemdmaltemd

analyzing-survey-results

Analyze survey data to extract insights and generate structured reports.

Community
Intermediate