qa-coverage-report

Convert QA audit issue logs into a deduplicated coverage report and terminal summary.

Updated May 22, 2026
One-click install
npx skills add https://github.com/Luqman-Ud-Din/blackbox-qa-agent --skill qa-coverage-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-coverage-report
Source: https://github.com/Luqman-Ud-Din/blackbox-qa-agent/tree/main/skills/qa-coverage-report
Command: npx skills add https://github.com/Luqman-Ud-Din/blackbox-qa-agent --skill qa-coverage-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns raw QA issue logs into a concise coverage report, helping teams quickly understand what was tested, what defects were found, and how much of the audit completed successfully.

Core Features & Use Cases

  • Issue Deduplication: Reads all issue records from the audit run and keeps only the first instance of each issue ID.
  • Coverage Reporting: Aggregates issues by severity, skill, route, and viewport to show audit completeness at a glance.
  • Run Summary Output: Writes a compact JSON report and prints a terminal summary with totals, bug counts, and chronic issue notes.
  • Use Case: After a large automated QA sweep, use this Skill to produce a final report for stakeholders without manually consolidating logs.

Quick Start

Use the qa-coverage-report skill to read the latest QA run artifacts and generate a final coverage summary.

Frequently Asked Questions about qa-coverage-report

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

FAQPage Schema
How do I generate a coverage report from JSONL issue logs after an automated QA audit?

To generate a coverage report from JSONL issue logs, parse the issue streams from your audit run directory and aggregate the data by route, viewport, and severity to output a consolidated coverage-report.json file.

What is the best way to deduplicate QA audit issues before reporting?

Issue deduplication for QA reporting works by reading all issue records from the audit run and keeping only the first instance of each specific issue ID to ensure final coverage metrics are not skewed by duplicate entries.

How does a coverage report summarize QA audit completeness by route and viewport?

A QA coverage report summarizes audit completeness by parsing issue logs and aggregating counts by route and viewport, providing a clear view of tested paths alongside severity metrics and bug-filing statistics.

Can I use Azure DevOps run state artifacts to produce a terminal summary of bug counts?

Yes, you can use Azure DevOps run state artifacts stored in the temporary run directory to produce a terminal summary that prints totals, bug counts, and chronic issue notes directly in the console.

What limitations exist when parsing JSONL issue streams for QA coverage reporting?

Coverage reporting from JSONL issue streams is limited to completed automated audits that store issue files, run state, and audit plans under a temporary run directory, requiring these specific artifacts to function properly.