skills.rest
nocnocgroup
nocnocgroupOFFICIAL
Explore all skills by this author →
WebsiteGitHub

retro

Aggregate commits, PRs, and test activity into team retrospectives.

Updated Mar 21, 2026
Search Tags:#git#storytelling#analytics#metrics#engineering#retro
One-click install
npx skills add https://github.com/nocnocgroup/gstack --skill retro-nocnocgroup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/nocnocgroup/gstack/tree/main/retro
Command: npx skills add https://github.com/nocnocgroup/gstack --skill retro-nocnocgroup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives provide a structured view of team work by analyzing commits, code changes, and test activity to surface per-person praise and growth opportunities.

Core Features & Use Cases

  • Per-author contribution breakdown with focus areas and growth suggestions.
  • Time-window based reporting (7d by default, adjustable windows) with a narrative summary.
  • Narratives that interpret patterns in focus, velocity, test discipline, and shipping cadence.
  • Auto-generation of a narrative for weekly planning and sprint retrospectives.

Quick Start

Invoke the /retro command to generate the current week's retrospective and view the narrative in the CLI or UI.

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 commits and PRs?▼

Generate a weekly engineering retrospective by invoking the /retro command, which aggregates git commits, pull requests, and test activity within a configurable time window to produce a narrative summary of team contributions.

What is a team-aware engineering retrospective?▼

A team-aware engineering retrospective analyzes per-author contributions, focus areas, and growth opportunities by consuming git data and test signals, producing a narrative that interprets patterns in velocity, test discipline, and shipping cadence.

Can I adjust the time window for sprint retrospective analysis?▼

Yes, the time window is configurable for sprint retrospective analysis, defaulting to 7 days but adjustable to accommodate project milestones or longer reporting periods as needed.

What git and test data is needed to produce per-author contribution breakdowns?▼

Producing per-author contribution breakdowns requires git commit history, pull request data, and test activity signals, with optional local analytics integrated when available to enrich the narrative output.

How do narrative summaries interpret engineering team focus and velocity?▼

Narrative summaries interpret engineering team focus and velocity by analyzing patterns in commit activity, test discipline, and shipping cadence, translating raw metrics into structured insights for weekly planning and retrospectives.

Does the retrospective analysis work for project milestones as well as weekly sprints?▼

Yes, retrospective analysis applies to both weekly sprints and project milestones, using adjustable time windows to capture the relevant git data and test signals for the specified reporting period.

Related Skills

Explore More Software Engineering Skills→
YuvaseeYuvasee
10

summary

Summarize code changes between git branches for Pull Request descriptions.

Community
Basic
SeaLion-hubSeaLion-hub

retro

Analyze commit history and contribution patterns to generate weekly engineering retrospective reports.

Community
Advanced
JacksonZx535JacksonZx535

retro

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

Community
Advanced
tygwantygwan
1

sprint

Control sprint lifecycles and track velocity and burndown metrics.

Community
Basic