skills.rest
Dragoon0x
Dragoon0xCOMMUNITY
Explore all skills by this author →
Website𝕏@0xDragoonLabGitHub

retro

Compile git metrics into structured weekly retro markdown files.

4|Updated Apr 11, 2026
Search Tags:#engineering workflow#retro#sprint retrospective#git metrics#weekly retro#team retro
One-click install
npx skills add https://github.com/Dragoon0x/dragoon-skills --skill retro-dragoon0x
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/Dragoon0x/dragoon-skills/tree/main/skills/retro
Command: npx skills add https://github.com/Dragoon0x/dragoon-skills --skill retro-dragoon0x

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manually compiling git statistics and structuring consistent weekly or sprint retros for engineering teams wastes time and often results in incomplete tracking of team output and process improvements.

Core Features & Use Cases

  • Preloaded Git Metrics: Automatically pulls commit counts, files changed, line diffs, and contributor data for the selected time period.
  • Structured Retro Template: Enforces a consistent format covering shipped work, blockers, learnings, and actionable process improvements.
  • Use Case: Engineering teams can run end-of-sprint retros without manually compiling version control data, ensuring every retro includes objective metrics on team output and quality trends.

Quick Start

Request your AI coding agent to generate a structured weekly retro for the most recent work period, preloaded with your team's git commit and contribution metrics.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I automate sprint retrospectives with git metrics?▼

Automated sprint retrospectives compile commit counts, line diffs, and contributor statistics from git, then generate a structured markdown retro template with shipped work, blockers, learnings, and process improvements.

What is the best way to generate a weekly retro template from git commits?▼

Generating a weekly retro template from git commits involves pulling version control metrics for the period and populating enforced markdown sections for shipped work and blockers, saving the file to the retros directory.

Does a sprint retrospective need preloaded git contribution statistics?▼

Sprint retrospectives need preloaded git contribution statistics to provide objective metrics on team output and quality trends, replacing manually compiled data that wastes time and risks incomplete tracking.

Can I run an ad-hoc team retro using git version control data?▼

Ad-hoc team retros can be run using git version control data by compiling contributor statistics and line diffs for a selected time period, producing a structured markdown file with actionable process improvements.

What limitations exist when generating retros from git metrics?▼

Generating retros from git metrics is limited to data available in version control, meaning qualitative blockers and learnings require manual input despite the automated commit counts and line diff compilation.

Related Skills

Explore More Software Engineering Skills→
ulle73ulle73

release-changelog

Generates Markdown release changelogs from git commit history and changeset data.

Community
Advanced
carson-sweetcarson-sweet
6

postmortem

Creates post-mortem documentation from git logs and generates issue tracking items.

Community
Advanced
Extremez-SuryaExtremez-Surya

release

Automate the release process for vercel-plugin with gates, version bump, artifacts, commit, and push.

Community
Advanced
jorgeavaldezjorgeavaldez
1

commit

Generate a one-line commit message from current working directory diffs.

Community
Intermediate