metrics

Analyzes time-series repository health metrics to identify trends and root causes.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/bkrsna/gemini-cli --skill metrics-bkrsna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: metrics
Source: https://github.com/bkrsna/gemini-cli/tree/main/tools/gemini-cli-bot/.gemini/skills/metrics
Command: npx skills add https://github.com/bkrsna/gemini-cli --skill metrics-bkrsna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Repository maintainers struggle to spot deteriorating health trends—such as rising PR latency or growing issue backlogs—hidden inside raw metrics data, and often lack a systematic way to investigate root causes before proposing workflow changes. ## Core Features & Use Cases - Time-Series Trend Analysis: Loads metrics-timeseries.csv to detect anomalies like increasing PR latency, growing open issues, or abnormal Actions and Gemini usage costs. - Hypothesis-Driven Root Cause Investigation: Develops competing hypotheses, gathers evidence via the gh CLI and GraphQL, and selects the explanation best supported by data. - Workload-Aware Recommendations: Assesses maintainer capacity and identifies whether bottlenecks sit with authors, maintainers, or CI infrastructure before proposing interventions. - Use Case: A maintainer notices review turnaround slowing over several weeks; this Skill analyzes the metrics history, tests hypotheses about reviewer overload versus CI delays, and proposes a systemic fix such as automated routing instead of more pings. ## Quick Start Analyze the repository metrics history to find the most significant deteriorating trend, investigate its root cause, and report your findings.

Frequently Asked Questions about metrics

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

FAQPage Schema
How do I analyze repository health metrics over time?

Load the metrics-timeseries.csv history and compare it against recent point-in-time snapshots to identify significant anomalies or deteriorating trends, such as steadily increasing PR latency or open issues growing faster than closure rates.

How to find the root cause of rising PR latency in GitHub?

Develop multiple competing hypotheses, then gather evidence for each using the gh CLI and GraphQL queries. Select the root cause most strongly supported by the collected data rather than assuming a single explanation.

Can this Skill create pull requests with its proposed changes?

Only when the orchestrator's System Directive enables PR creation; in that case it activates the prs skill to stage changes and generate a PR description. Otherwise it reports findings without staging any file changes.

When should the Gemini CLI be used in metrics analysis scripts?

Use the Gemini CLI only for classification tasks like sentiment analysis or semantic labeling when deterministic TypeScript or Git logic cannot achieve equivalent quality. It must never be used for execution or decision-making, and scripts must rely on default repository policies.

What are the limitations of proposing maintainer-driven fixes?

If the ratio of open unactioned work to active maintainers indicates overload, solutions that generate more pings are avoided. The Skill instead prioritizes systemic triage, automated routing, or auto-closure reflexes.