qa-metrics

Define QA metrics with formulas, targets, and CI automation hooks.

64|12|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/petrkindlmann/qa-skills --skill qa-metrics-petrkindlmann
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-metrics
Source: https://github.com/petrkindlmann/qa-skills/tree/main/skills/qa-metrics
Command: npx skills add https://github.com/petrkindlmann/qa-skills --skill qa-metrics-petrkindlmann

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Define, track, and act on QA metrics to improve software quality across teams and releases, turning data into actionable decisions.

Core Features & Use Cases

  • Comprehensive metric definitions, formulas, and targets for coverage, flakiness, MTTR, and defect escape.
  • Guidance to build dashboards and governance for product teams, engineering managers, and QA leads.
  • Use Case: When shipping a release, compare last sprint metrics to baseline to decide quality gates, and surface top issues.

Quick Start

Start by selecting three core QA metrics, connect your CI and issue tracker to begin collecting baselines, and monitor early trends.

Frequently Asked Questions about qa-metrics

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

FAQPage Schema
How do I define and track QA metrics to improve software quality across releases?

To track QA metrics effectively, select core measures like coverage, flakiness, MTTR, and defect escape, then connect your CI and issue tracker to collect baselines and monitor early trends for actionable quality decisions.

What is defect escape rate and how is it used in QA governance?

Defect escape rate measures issues reaching production versus those caught internally. It serves as a core QA metric with defined formulas and targets to establish governance, compare sprint metrics to baselines, and decide release quality gates.

How do I set up dashboards to monitor test flakiness and coverage in CI/CD pipelines?

Setting up dashboards involves using provided metric formulas and automation hooks to pull flakiness and coverage data from your CI systems and issue trackers, enabling product teams and QA leads to visualize trends and enforce quality gates.

Can I use this approach to compare sprint metrics against a baseline before shipping a release?

Yes, when shipping a release you can compare last sprint metrics to your established baseline using the provided formulas and targets, allowing you to decide quality gates and surface top issues for continuous improvement.

Do I need specific CI systems or issue trackers to automate QA metric collection?

You need access to a CI system and an issue tracker to establish automated data collection. The approach provides automation hooks to connect these existing platforms, pulling raw data to calculate metrics like MTTR and flakiness without requiring specific proprietary tools.