skills.rest
Intension-us
Intension-usOFFICIAL
Explore all skills by this author →
GitHub

retro

Analyze Git commit history and code quality metrics to generate weekly engineering retrospectives.

Updated Apr 3, 2026
Search Tags:#git#metrics#engineering#code-quality#team#retro
One-click install
npx skills add https://github.com/Intension-us/attention-diagnostic --skill retro-intension-us
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/Intension-us/attention-diagnostic/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/Intension-us/attention-diagnostic --skill retro-intension-us

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives that analyze commit history, work patterns, and code quality metrics with persistent context, delivering team-aware praise and growth opportunities.

Core Features & Use Cases

  • Analyzes commits and per-person contributions to surface praise and growth opportunities.
  • Tracks trends over time and highlights hotspots in the codebase to inform process improvements.
  • Proactively suggests actionable improvements at the end of a work week or sprint to improve velocity and code quality.

Quick Start

Run /retro to generate a weekly engineering retrospective for the current repository and window.

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 git commit history?▼

Automate engineering retrospectives by running a command that analyzes git commit history, work patterns, and code quality metrics to generate a structured weekly report with per-person praise and growth suggestions.

Can I generate code quality metrics and team feedback for a custom sprint window?▼

Yes, generate code quality metrics and team feedback for custom sprint windows by defining your desired time range, which analyzes commits and file changes to highlight codebase hotspots and trends.

What git data do I need to generate a team retrospective report?▼

Generating a team retrospective report requires access to git history, authors, timestamps, and file changes to analyze per-person contributions and surface actionable growth opportunities.

How do code quality metrics from commit history improve team velocity?▼

Code quality metrics from commit history improve team velocity by tracking trends over time, highlighting codebase hotspots, and proactively suggesting actionable process improvements at the end of a work week.

Does this engineering retrospective tool work with standard weekly sprints?▼

Yes, this engineering retrospective tool works with standard weekly sprints and custom time windows, analyzing per-person contributions to deliver team-aware praise and growth opportunities.

Related Skills

Explore More Software Engineering Skills→
26mitch2626mitch26

gstack-openclaw-retro

Analyze Git commit history to generate engineering retrospective reports.

Community
Advanced
wodehwodeh

retro

Analyze commit history and code-quality metrics to generate weekly engineering retrospectives.

Community
Advanced
koderoverkoderover
7

sonar

Retrieve and analyze SonarQube code quality metrics and quality gate statuses.

Official
Intermediate
shekerkammashekerkamma

retro

Analyze git commit history and code quality metrics to generate weekly engineering retrospective reports.

Community
Advanced