skills.rest
tranvietanh0
tranvietanh0COMMUNITY
Explore all skills by this author →
GitHub

t1k-retro

Analyze git metrics and generate sprint retrospective reports.

Updated Apr 8, 2026
Search Tags:#git#metrics#retrospective#review#sprint
One-click install
npx skills add https://github.com/tranvietanh0/StackTheRing --skill t1k-retro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: t1k-retro
Source: https://github.com/tranvietanh0/StackTheRing/tree/main/.claude/skills/t1k-retro
Command: npx skills add https://github.com/tranvietanh0/StackTheRing --skill t1k-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, node.js, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides data-driven sprint retrospectives, helping teams analyze git metrics for sprint reviews, commit analysis, code health indicators, and team velocity.

Core Features & Use Cases

  • Git Metrics Analysis: Gather objective git metrics such as commit frequency, code churn, and test-to-code ratio.
  • Retro Report Generation: Automatically generate an actionable retrospective report based on the analyzed metrics.
  • Customization: Supports customization through command-line arguments like timeframe, team comparison, and output format.

Quick Start

Use the t1k:retro skill to generate a sprint retrospective report for the last 7 days.

Frequently Asked Questions about t1k-retro

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

FAQPage Schema
How do I generate a data-driven sprint retrospective report from git metrics?▼

To generate a sprint retrospective report, this Skill automates the extraction of git metrics like commit frequency and code churn. It analyzes your repository within a specified timeframe and outputs a detailed review document for your team.

What git metrics are analyzed for sprint reviews?▼

Sprint reviews analyze specific git metrics including commit frequency, code churn, and test-to-code ratio. These indicators provide objective data on code health and team velocity to help drive retrospective discussions.

Do I need GitHub CLI and Node.js to run git metrics analysis?▼

Yes, running git metrics analysis requires a Node.js environment, git, and the gh CLI. The GitHub CLI is specifically used to fetch issue data, while Node.js executes the analysis scripts to process repository history.

Can I customize the timeframe for a git retrospective report?▼

Yes, you can customize the git retrospective report timeframe using command-line arguments. This allows you to target specific sprint durations, compare team performance across periods, and adjust the output format to fit your workflow.

What is the best way to track team velocity using git history?▼

Tracking team velocity through git history is best accomplished by analyzing commit frequency and code churn over a defined sprint interval. This approach provides objective, data-driven insights into development pace and code stability.

Related Skills

Explore More Software Engineering Skills→
script-reposcript-repo

github-workflow-automation

Automate GitHub Actions workflows with AI swarm coordination and CI/CD orchestration.

Community
Advanced
bitwardenbitwarden
129

retrospecting

Generate structured retrospective reports from Claude Code session data.

Official
Intermediate
CornjebusCornjebus
1

github-project-management

Automate GitHub issue triage, board synchronization, and sprint planning.

Community
Intermediate
roanbrasilroanbrasil
5

static-analysis

Automate static analysis for Java, Kotlin, Python, and Rust codebases.

Community
Advanced