github-metrics

Collect engineering metrics from GitHub APIs and analyze PR cycle time.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/3horizons/agentic-devops-platform --skill github-metrics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-metrics
Source: https://github.com/3horizons/agentic-devops-platform/tree/main/.github/skills/github-metrics
Command: npx skills add https://github.com/3horizons/agentic-devops-platform --skill github-metrics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, curl, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the collection and analysis of key engineering metrics directly from GitHub, providing visibility into development velocity, release cadence, and CI/CD health.

Core Features & Use Cases

  • PR Cycle Time: Measure the time from pull request creation to merging.
  • Deployment Frequency: Track how often code is deployed to production.
  • CI/CD Health: Analyze workflow success rates and average durations.
  • Contributor Activity: Understand commit patterns and contributions.
  • Use Case: A development manager can use this skill to generate a weekly report on PR cycle times and deployment frequency to identify bottlenecks and celebrate team achievements.

Quick Start

Use the github-metrics skill to collect pull request cycle time metrics for the last 30 days.

Frequently Asked Questions about github-metrics

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

FAQPage Schema
How do I collect GitHub engineering metrics for PR cycle time and deployment frequency?

To collect GitHub engineering metrics, this Skill automates the retrieval of pull requests, deployments, and releases from GitHub APIs to analyze PR cycle time, deployment frequency, and CI/CD pipeline health. It requires GitHub CLI authentication and specific repository scopes to gather the data.

Do I need GitHub CLI authentication to analyze CI/CD pipeline health and workflow runs?

Yes, GitHub CLI authentication is required to analyze CI/CD pipeline health and workflow runs. The Skill depends on specific repository scopes to access GitHub APIs for retrieving workflow success rates, average durations, and contributor activity data.

Can I use curl and jq to track Dora metrics and release cadence from GitHub?

Yes, you can use curl and jq to track Dora metrics and release cadence because the Skill depends on these tools to process GitHub API responses. It analyzes deployment frequency, release cadence, and PR review latency to provide engineering intelligence.

What's the best way to generate a weekly report on contributor activity and commit patterns?

The best way to generate a weekly report on contributor activity is to use this Skill to collect commit patterns and PR review latency from GitHub APIs. It provides visibility into development velocity and team contributions to identify bottlenecks and celebrate achievements.

Does this approach work for analyzing engineering intelligence across multiple repositories?

This approach works for analyzing engineering intelligence across repositories by collecting metrics from GitHub APIs, provided the authenticated GitHub CLI has the specific repository scopes required. It measures PR cycle time, deployment frequency, and CI/CD health for the targeted repositories.