Agent-skills-standard quality-engineering-zephyr-coverage-analysis
Audit test coverage health, gaps, and QE debt for Jira stories or epics. Produces coverage_analysis_report.md with AC-to-TC heatmap, risk scores, and prioritized action plan. Use when assessing coverage percentage, pre-release readiness, sprint readiness, or identifying missing test cases. Do NOT use for TC creation — use zephyr-test-generation instead. (triggers: coverage analysis, test coverage, coverage gaps, QE debt, QE audit, pre-release readiness, sprint readiness, coverage_analysis_report.md, zephyr coverage, test gap, AC coverage, test-ready)
install
source · Clone the upstream repo
git clone https://github.com/HoangNguyen0403/agent-skills-standard
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/HoangNguyen0403/agent-skills-standard "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/quality-engineering/quality-engineering-zephyr-coverage-analysis" ~/.claude/skills/hoangnguyen0403-agent-skills-standard-quality-engineering-zephyr-coverage-analys && rm -rf "$T"
manifest:
skills/quality-engineering/quality-engineering-zephyr-coverage-analysis/SKILL.mdsource content
Zephyr Coverage Analysis
Priority: P1 (HIGH)
Workflow
CRITICAL — Read and follow workflow file exactly. NOT implement from memory or from this description. Implementing inline bypasses
andjira-analystsub-agents.zephyr-scanner
Read and execute
.agent/workflows/zephyr-coverage-analysis.md.
Anti-Patterns
- No TC creation: Analysis read-only — call quality-engineering-zephyr-test-generation to create TCs.
- No pagination-first: Always use
(direct lookup) before falling back to pagination.Get Issue Link Test Cases - No ticket-level platform: Read Platform from each AC table row HTML, not ticket header section.
- No merged WEB+MOBILE slots: Treat each platform as independent coverage slot — Mobile covered ≠ Web covered.
- No skipping QE debt: Scan beyond AC rows — always include data correctness, negative flows, role differentiation, and regression risk in Section 4.
References
- Report Template — load when building coverage_analysis_report.md (Step 5 of workflow)
- Impact Analysis Protocol — TC discovery protocol
- Zephyr Test Generation — invoke after analysis to create missing TCs