dora-metrics

Calculate DORA metrics from git history and deployment logs.

3|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/jholhewres/devclaw-skills --skill dora-metrics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dora-metrics
Source: https://github.com/jholhewres/devclaw-skills/tree/main/skills/dora-metrics
Command: npx skills add https://github.com/jholhewres/devclaw-skills --skill dora-metrics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps development teams understand and improve their performance by calculating key DORA metrics, providing insights into deployment frequency, lead time, change failure rate, and mean time to recovery.

Core Features & Use Cases

  • Deployment Frequency: Tracks how often code is successfully deployed to production.
  • Lead Time for Changes: Measures the time from code commit to production deployment.
  • Change Failure Rate: Calculates the percentage of deployments causing a failure in production.
  • Mean Time to Recovery (MTTR): Determines how long it takes to restore service after a production failure.
  • Use Case: A team lead can use this skill at the end of a sprint to assess their team's delivery performance against industry benchmarks and identify areas for improvement.

Quick Start

Calculate DORA metrics for the current repository.

Frequently Asked Questions about dora-metrics

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

FAQPage Schema
How do I calculate DORA metrics from git history and deployment logs?

To calculate DORA metrics from git history, you need a tool that analyzes commit timestamps, pull requests, and deployment tags. This Skill processes that git data to measure your team's deployment frequency, lead time, change failure rate, and mean time to recovery automatically.

What are DORA metrics and how do they measure dev team performance?

DORA metrics are four key indicators used to measure dev team performance: deployment frequency, lead time for changes, change failure rate, and mean time to recovery. They help engineering teams assess delivery speed and stability against industry benchmarks.

Do I need gh CLI installed to measure lead time and deployment frequency?

Yes, you need both git and gh CLI installed to measure lead time and deployment frequency. The Skill requires gh CLI to access your commit history, pull requests, and issues for accurate analysis of your software development team's delivery performance.

Can I assess my team's delivery performance against industry benchmarks at sprint end?

You can assess your team's delivery performance against industry benchmarks at sprint end by analyzing your repository's git history. This Skill calculates your DORA metrics to help team leads identify areas for improvement in deployment speed and stability.

What's the best way to track change failure rate and mean time to recovery?

The best way to track change failure rate and mean time to recovery is by analyzing git history and deployment logs together. This Skill calculates the percentage of deployments causing failures and determines how long it takes to restore service after a production failure.