skills.rest
DariusCorvus
DariusCorvusCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

retro

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

37|2|Updated Mar 28, 2026
Search Tags:#git#metrics#engineering#code-quality#retro#team-feedback
One-click install
npx skills add https://github.com/DariusCorvus/iqualize --skill retro-dariuscorvus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/DariusCorvus/iqualize/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/DariusCorvus/iqualize --skill retro-dariuscorvus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retros analyze commit history, work patterns, and code quality metrics to provide a persistent, team-aware view of how work unfolds over time. This helps engineering teams identify strengths, growth opportunities, and recurring patterns to improve delivery.

Core Features & Use Cases

  • Per-person contribution breakdown with praise and growth areas.
  • Persistent history and trend tracking across sprints and weeks.
  • Proactive suggestions for end-of-week or sprint wrap-up discussions.

Quick Start

Run the /retro command to generate a weekly engineering retrospective for the current time window.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate a weekly engineering retrospective from git commit history?▼

Generate a weekly engineering retrospective by analyzing git commit history, work patterns, and code quality metrics to produce per-person contributions with praise and growth areas.

What is the best way to track persistent code quality trends across engineering sprints?▼

Tracking persistent code quality trends across sprints involves analyzing commit history and work patterns to maintain a team-aware view of recurring patterns and growth opportunities over time.

Can I get per-person contribution breakdowns with feedback for my engineering team?▼

Yes, you can get per-person contribution breakdowns that highlight individual praise and growth areas by analyzing code quality metrics and work patterns from your team's development history.

How do I prepare sprint wrap-up discussions using code quality metrics and team feedback?▼

Prepare sprint wrap-up discussions by analyzing work patterns and code quality metrics to generate proactive suggestions and team-aware insights for end-of-week engineering reviews.

Does weekly engineering retro analysis require any specific dependencies or components?▼

Weekly engineering retro analysis requires no external dependencies or components, operating directly on git commit history and work patterns to generate growth insights and team feedback.

Related Skills

Explore More Software Engineering Skills→
garrytangarrytan
127.1k

gstack-openclaw-retro

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

Community
Advanced
JeremiahEllingtonJeremiahEllington

retro

Analyze git commit history and work patterns to generate team-wide retrospectives with per-person insights.

Community
Advanced
joeylife94joeylife94

retro

Analyze git commit history and code quality metrics for weekly engineering retrospectives.

Community
Advanced
tygwantygwan
1

sprint

Control sprint lifecycles and track velocity and burndown metrics.

Community
Basic