skills.rest
lengo0951
lengo0951COMMUNITY
Explore all skills by this author →
𝕏@quocngo04GitHub

ck:retro

Analyze git metrics and generate structured markdown or HTML retrospective reports.

Updated Apr 18, 2026
Search Tags:#report generation#retrospective#sprint review#git analysis#data-driven insights
One-click install
npx skills add https://github.com/lengo0951/pms --skill ck-retro-lengo0951
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:retro
Source: https://github.com/lengo0951/pms/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/lengo0951/pms --skill ck-retro-lengo0951

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of manual, subjective sprint retrospectives by leveraging data from git metrics to provide a more objective and insightful review process.

Core Features & Use Cases

  • Data-Driven Retrospectives: Utilizes git metrics to compute health indicators and generate a structured report.
  • Customizable Reports: Outputs markdown or HTML reports with options for timeframe, team breakdown, and format.
  • Use Case: After a sprint, use this Skill to automatically generate a comprehensive report on team activity, code health, and plan completion, providing actionable insights for improvement.

Quick Start

Run the ck:retro skill with the timeframe 'sprint' to generate a retrospective report for the current sprint.

Frequently Asked Questions about ck: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?▼

You can generate a data-driven sprint retrospective report by running this Skill to automate git metrics analysis, computing health indicators and outputting a structured markdown or HTML report for your selected timeframe.

What are the benefits of using git analysis for sprint reviews instead of manual tracking?▼

Using git analysis for sprint reviews replaces subjective manual tracking with objective data-driven insights, automatically computing code health and team activity metrics directly from repository history to provide actionable improvement feedback.

Do I need the gh CLI installed to track issues during a sprint retrospective?▼

You need git installed, and potentially the gh CLI if your sprint retrospective requires issue tracking. These dependencies allow the Skill to automatically pull repository metrics and generate the retrospective report.

Can I customize the timeframe and format for retrospective report generation?▼

Yes, you can customize retrospective report generation by specifying options for the timeframe, team breakdown, and output format, allowing you to target the exact sprint period and output either markdown or HTML.

What is the best way to review code health and plan completion after a sprint?▼

The best way to review code health and plan completion after a sprint is to automate git metrics analysis, generating a comprehensive report on team activity and code status to provide actionable insights for improvement.

Why should I use automated git metrics for sprint reviews rather than manual retrospectives?▼

Automated git metrics for sprint reviews eliminate the manual effort and subjectivity of traditional retrospectives, leveraging repository data to provide a more objective and insightful review of code health and plan completion.

Related Skills

Explore More Software Engineering Skills→
tranvietanh0tranvietanh0

t1k-retro

Analyze git metrics and generate sprint retrospective reports.

Community
Advanced
bitwardenbitwarden
129

retrospecting

Generate structured retrospective reports from Claude Code session data.

Official
Intermediate
khapn-2933khapn-2933

tkm:run-retro

Generate sprint retrospective reports from git repository history.

Community
Advanced
fagemxfagemx
58

game-retro

Generate sprint health and milestone progress reports from git history and project artifacts.

Community
Advanced