Zephyr Coverage Analysis

This is a read-only audit tool that pulls a Jira story, scrapes its acceptance criteria table (including those color-coded platform tags), finds related Zephyr test cases, and maps coverage per platform with risk scoring. It runs two parallel sub-agents to keep API noise out of context, then generates a management report with gaps, quality issues in existing tests, and a prioritized action plan. The AC-to-TC mapping logic is solid: it distinguishes between covered, partial, and not covered based on scope matching, and it flags realistic QE debt like missing data validation or negative flow coverage. If you're tired of manually auditing test coverage before release and need something that produces an actual artifact your QE manager can act on, this does the job.

GitHub stars: 504
last updated: Jun 11, 2026

View on GitHub

Install

$ npx -y skills add hoangnguyen0403/agent-skills-standard --skill zephyr-coverage-analysis --agent claude-code

Installs into .claude/skills of the current project.

Files

Zephyr Coverage Analysis Skill

[!IMPORTANT] Analyze Zephyr test case coverage for a Jira user story and produce a QE management report with metrics, risk scoring, and prioritized recommendations.

Instructions

When the user asks to perform this workflow, execute the following steps:

Read-only audit — produces coverage_analysis_report.md, does NOT create or modify Zephyr test cases

// turbo-all

1. Gather Input

If the Jira Issue Key is not provided, ask for it.

Optional: Scope (single ticket default, or comma-separated epic/sprint keys) | Depth (quick = coverage table only, full = default with risk scoring + QE observations).