skills.rest
himes19
himes19COMMUNITY
Explore all skills by this author →
GitHub

retro

Generate a weekly retrospective report with developer stats, shipping streaks, and test health trends.

Updated Apr 12, 2026
Search Tags:#retrospective#test-health#weekly-checkin#team-growth#engineering-stats#ship-tracking
One-click install
npx skills add https://github.com/himes19/pulsevolt-infra --skill retro-himes19
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/himes19/pulsevolt-infra/tree/main/skills/gstack/retro
Command: npx skills add https://github.com/himes19/pulsevolt-infra --skill retro-himes19

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospective with developer stats, shipping streaks, test health trends, and growth opportunities. Use for weekly check-ins or when asked for a retrospective.

Core Features & Use Cases

  • Structured weekly retrospective format that blends quantitative data with qualitative reflection.
  • Data collection prompts: Git stats (last 7 days), PR activity, and test health to surface actionable insights.
  • Use Case: run a weekly check-in to review shipping streaks, identify growth opportunities, and align on next steps.

Quick Start

Generate a weekly retrospective report using the latest Git stats, PR activity, and test results to inform team improvements.

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 dev retrospective report with engineering stats?▼

A weekly retrospective combines developer stats, shipping streaks, and test health trends into a structured Markdown format. It surfaces actionable insights across sections for velocity, wins, concerns, and next steps during sprint reviews.

What data do I need for a sprint review retrospective with shipping streaks and test health?▼

Sprint review retrospectives require Git stats from the last 7 days, PR activity, and test health results. These data points identify growth opportunities and align engineering teams on actionable next steps.

Can I use a weekly check-in to track developer stats and team growth opportunities?▼

Yes, weekly check-ins track developer stats and team growth opportunities by blending quantitative data with qualitative reflection. This retrospective process surfaces actionable insights to drive continuous engineering team improvements.

What is the best way to structure a retrospective with velocity and test health trends?▼

Structure a retrospective using a Markdown format with dedicated sections for stats, velocity, wins, concerns, and next steps. This layout blends quantitative engineering data with qualitative reflection to produce actionable team outputs.

Does a weekly retrospective report require external dependencies to analyze PR activity?▼

No, generating a weekly retrospective report requires no external dependencies to analyze PR activity. It operates independently to process Git stats and test health data, outputting structured Markdown for sprint reviews.

Related Skills

Explore More Software Engineering Skills→
rkumar261rkumar261
1

retro

Generate weekly engineering retrospectives from git logs, tests, and PR activity.

Community
Advanced
shogo-labsshogo-labs
12

retro

Generates weekly engineering retrospective reports from repository commit history and team data.

Official
Advanced
aspectrraspectrr

retro

Generates weekly developer performance and health retrospectives from Git stats, PR metrics, and test results.

Community
Intermediate
89jobrien89jobrien
4

agile-ceremonies

Structure Agile standups, retrospectives, and sprint tracking with action items.

Community
Intermediate