retro

Name: retro
Availability: InStock
Author: jacksonzx535

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

Updated Mar 25, 2026

Search Tags:#code quality #retrospective #commit history #team analysis #work patterns

Ready to run

npx skills add https://github.com/JacksonZx535/kingsight --skill retro-jacksonzx535

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/JacksonZx535/kingsight/tree/main/retro
Command: npx skills add https://github.com/JacksonZx535/kingsight --skill retro-jacksonzx535

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a comprehensive weekly engineering retrospective, analyzing commit history, work patterns, and code quality metrics, enabling teams to gain insights and improve their workflow.

Core Features & Use Cases

Commit History Analysis: Analyze all commits in a specified time window to identify patterns, such as hotspots, session distribution, and author contributions.
Code Quality Metrics: Measure key metrics like LOC, test coverage, and commit type distribution to assess code health.
Team Awareness: Identify top contributors, highlight achievements, and provide constructive feedback for improvement opportunities.

Quick Start

Run the /retro command to generate a retrospective report for the last 7 days.

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?▼

Generate a weekly engineering retrospective by running the `/retro` command, which uses Git commands to fetch and analyze commit history. The resulting report calculates total commits, author contributions, and test coverage ratio for the specified time window.

What code quality metrics are included in a Git retrospective report?▼

A Git retrospective report includes code quality metrics such as lines of code, test coverage ratio, and commit type distribution. These metrics assess code health and identify improvement opportunities within the development workflow.

Can I visualize work patterns and code hotspots from my repository's commit data?▼

Yes, you can visualize work patterns and code hotspots from repository commit data. The retrospective report includes visualizations of time and session patterns, commit type breakdowns, and identifies codebase hotspots for the analyzed time window.

Does the retrospective analysis require any specific dependencies or external tools?▼

No specific external dependencies are required for retrospective analysis. The skill operates using built-in Git commands to fetch and analyze repository commit history, requiring only access to the repository's commit data.

How do I track team contributions and identify top contributors in a codebase?▼

Track team contributions and identify top contributors by generating a retrospective report that analyzes commits within a specified time window. The report calculates contributions per author, highlights achievements, and provides constructive feedback for improvement opportunities.

What is the best way to measure developer work patterns and session distribution?▼

The best way to measure developer work patterns and session distribution is by analyzing commit history over a specified time window. This generates visualizations of time and session patterns, revealing workflow trends and codebase hotspots for team awareness.