skills.rest
aspectrr
aspectrrCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

retro

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

Updated Apr 20, 2026
Search Tags:#retrospective#retro#team-reflection#growth-opportunities#test-health#shipping-streaks#developer-stats
One-click install
npx skills add https://github.com/aspectrr/denchclaw-workspace --skill retro-aspectrr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/aspectrr/denchclaw-workspace/tree/main/skills/gstack/retro
Command: npx skills add https://github.com/aspectrr/denchclaw-workspace --skill retro-aspectrr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retros run with a focus on developer performance by blending quantitative stats with qualitative reflections, helping teams capture learnings without manual synthesis.

Core Features & Use Cases

  • Automated data collection: Pulls weekly Git stats, PR metrics, and test results to form a baseline.
  • Insightful storytelling: Combines numbers with narrative notes to surface growth opportunities and process improvements.
  • Structured weekly format: Provides a repeatable retro structure including wins, concerns, and planned actions for the next week.

Quick Start

Run the weekly retro for the current sprint to generate a summarized report for the team.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I automate weekly developer retrospectives using Git stats and PR metrics?▼

Automate weekly developer retrospectives by pulling Git stats, PR metrics, and test outcomes, then combining them with qualitative notes to generate a summarized retro narrative. This process captures learnings without requiring manual data synthesis.

What is a developer retrospective and how does it combine quantitative stats with qualitative reflections?▼

A developer retrospective is a weekly summary blending quantitative stats like shipping streaks with qualitative reflections. It applies across sprint cycles to surface growth opportunities, test health trends, and process improvements in a repeatable narrative format.

How do I track test health trends and shipping streaks across sprint cycles?▼

Track test health trends and shipping streaks across sprint cycles by applying a repeatable retrospective structure that collects weekly developer metrics. This identifies performance baselines and presents concerns and planned actions for the next week.

Can I generate a structured weekly retro report for my engineering team without manual synthesis?▼

Yes, you can generate a structured weekly retro report by automatically collecting weekly developer performance and health data. It formats quantitative metrics and qualitative notes into a repeatable narrative covering wins, concerns, and planned actions.

Does the weekly retrospective format work for continuous sprint cycles?▼

Yes, the weekly retrospective format works for continuous sprint cycles by applying a consistent structure to summarize developer performance. It maintains a repeatable narrative across iterations to track test health, shipping streaks, and growth opportunities over time.

Related Skills

Explore More Software Engineering Skills→
putrawitamaputrawitama
1

retro

Generate structured weekly retrospectives from git stats, PR data, and test results.

Community
Intermediate
himes19himes19

retro

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

Community
Intermediate
ivegamsftivegamsft

sprint-retrospective

Generate sprint retrospective documents with templates, metrics, and improvement tips.

Community
Intermediate
johnatas-henriquejohnatas-henrique

sprint-status

Aggregate sprint metrics and flag stale tasks from plan and story files.

Community
Intermediate