skills.rest
jmagly
jmaglyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

regression-metrics

Track regression rates, MTTD, MTTF, escape rate, and recurrence rate from test results.

175|26|Updated Aug 14, 2025
Search Tags:#testing#quality assurance#analytics#metrics#dashboard#regression
One-click install
npx skills add https://github.com/jmagly/aiwg --skill regression-metrics-jmagly
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: regression-metrics
Source: https://github.com/jmagly/aiwg/tree/main/plugins/sdlc/skills/regression-metrics
Command: npx skills add https://github.com/jmagly/aiwg --skill regression-metrics-jmagly

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of understanding and managing software regressions by providing detailed analytics on their occurrence, impact, and trends.

Core Features & Use Cases

  • Track Regression Rates: Monitor how often regressions are introduced per release or sprint.
  • Measure Detection & Fix Times: Analyze Mean Time To Detect (MTTD) and Mean Time To Fix (MTTF).
  • Identify Patterns & Hotspots: Pinpoint components or code areas prone to regressions.
  • Generate Dashboards: Visualize key metrics and trends for informed decision-making.
  • Use Case: A development lead can use this skill to quickly assess the quality trajectory of the latest release, identify if regressions are increasing, and pinpoint which modules require more attention.

Quick Start

Show me the regression metrics dashboard for the last 30 days.

Frequently Asked Questions about regression-metrics

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

FAQPage Schema
How do I calculate regression rate and escape rate from test results and issue tracker data?▼

You calculate regression rate and escape rate by parsing regression test results and issue tracker data to measure occurrence rates against release baselines. This yields key quality assurance metrics tracking how often regressions are introduced and escape detection.

What is Mean Time To Detect for software regressions and how is it measured?▼

Mean Time To Detect (MTTD) measures the average time taken to find software regressions after introduction. It is calculated by parsing historical records and bisect findings to analyze detection patterns and generate health dashboards for quality assurance.

How do I generate a dashboard tracking regression metrics over the last 30 days?▼

You generate a regression metrics dashboard by parsing test results and issue tracker data over the last 30 days. This visualizes occurrence rates, Mean Time To Detect, and Mean Time To Fix trends to assess release quality trajectory.

Can I pinpoint code hotspots prone to regressions using baseline comparisons?▼

Yes, you can pinpoint code hotspots by analyzing baseline comparisons and historical regression test results to identify patterns. This highlights specific components or code areas prone to recurring regressions for targeted process improvement.

Do I need issue tracker data to analyze regression statistics and recurrence rates?▼

Yes, issue tracker data is required to analyze regression statistics and calculate recurrence rates accurately. Parsing these records alongside bisect findings and test results provides the comprehensive context needed for quality assurance analytics.

Related Skills

Explore More Software Engineering Skills→
imonmiimonmi

benchmark

Compare baseline and PR performance metrics to detect regressions.

Community
Advanced
Davie521Davie521
7

skill-health

Aggregate and visualize portfolio health metrics across all skills.

Community
Advanced
alangebalangeb

test-suite-monitor

Run and monitor test suites in background tmux sessions with comparative analysis.

Community
Intermediate
Eigo-Mt-FujiEigo-Mt-Fuji

quality-assurance

Creates comprehensive QA strategies and test plans for software projects.

Community
Advanced