skills.rest
MonumentalSystems
MonumentalSystemsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

quality-metrics

Define QA standards for test coverage, code quality, and defect metrics.

17|5|Updated Feb 6, 2026
Search Tags:#quality gates#test coverage#qa metrics#cyclomatic complexity#kpi dashboard#defect density#maintainability index
One-click install
npx skills add https://github.com/MonumentalSystems/Atlas-Agent-Teams --skill quality-metrics-monumentalsystems
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quality-metrics
Source: https://github.com/MonumentalSystems/Atlas-Agent-Teams/tree/main/teams/qa-testing/skills/quality-metrics
Command: npx skills add https://github.com/MonumentalSystems/Atlas-Agent-Teams --skill quality-metrics-monumentalsystems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quantify software quality using test coverage, code quality signals, and defect metrics so you can make decisions based on evidence instead of opinions.

Core Features & Use Cases

  • Test Coverage Metrics: Line, branch, function, statement, and condition coverage with practical coverage targets for different code types.
  • Code Quality Metrics: Cyclomatic complexity, maintainability index, duplication rate, code smells, and technical debt ratio to pinpoint maintainability risks.
  • Defect Metrics & QA KPIs: Defect density, defect removal efficiency (DRE), defect leakage, defect age, and severity distribution to track reliability and release confidence.
  • Quality Gates & Reporting: Example gates for code, performance, and security, plus guidance for dashboards, reporting cadence, and continuous improvement.

Quick Start

Use the quality-metrics skill to define coverage, complexity, and defect targets for your next CI/CD release and quality dashboard.

Frequently Asked Questions about quality-metrics

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

FAQPage Schema
How do I define test coverage and code quality thresholds for CI/CD quality gates?▼

Defect density measures the number of defects per unit size of software, while DRE calculates the percentage of defects found before release versus after. Tracking both metrics provides release confidence and identifies reliability trends across development cycles.

What is the best way to track QA KPIs for continuous improvement across software teams?▼

Yes, you can monitor maintainability risks by tracking cyclomatic complexity, duplication rate, code smells, and technical debt ratio. These metrics pinpoint specific areas needing refactoring and help prioritize maintenance efforts across the codebase.

Why does defect leakage happen and how do I calculate it for release readiness reviews?▼

Defect leakage occurs when defects escape detection during testing and surface in production. You calculate it by comparing defects found post-release to total defects found, which quantifies QA effectiveness and informs release readiness decisions.

Does this approach work for setting different coverage targets for various code types?▼

Yes, this approach supports setting practical coverage targets tailored to different code types. You can establish varying thresholds for critical versus non-critical components, ensuring test coverage efforts align with risk levels and business priorities.

Related Skills

Explore More Software Engineering Skills→
Sheldon-92Sheldon-92
3

Testing

Execute test suites and report failures with coverage metrics.

Community
Intermediate
nateanatea

quality-metrics

Calculate and visualize software quality metrics for dashboards and CI/CD quality gates.

Community
Advanced
dinoudondinoudon

code-quality-metrics

Assess code quality using cyclomatic complexity, test coverage, and maintainability metrics.

Community
Advanced
shekerkammashekerkamma

guardrails

Pair success metrics with guardrail metrics to identify trade-offs in analytical workflows.

Community
Basic