quality-engineering-zephyr-coverage-analysis
Assesses Jira test coverage health and identifies QE debt for release readiness.
Install
mkdir -p .claude/skills/quality-engineering-zephyr-coverage-analysis && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10668" && unzip -o skill.zip -d .claude/skills/quality-engineering-zephyr-coverage-analysis && rm skill.zipInstalls to .claude/skills/quality-engineering-zephyr-coverage-analysis
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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.Key capabilities
- →Audit test coverage health
- →Identify QE debt
- →Generate AC-to-TC heatmaps
- →Assess pre-release readiness
- →Prioritize QE actions
How it works
The skill scans Jira tickets to map acceptance criteria to test cases, identifying coverage gaps and calculating risk scores to produce a structured audit report.
Inputs & outputs
When to use quality-engineering-zephyr-coverage-analysis
- →Audit test coverage
- →Identify QE debt
- →Check sprint readiness
- →Analyze AC coverage
About this skill
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
jira-analystandzephyr-scannersub-agents.
Read and execute .agents/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
Get Issue Link Test Cases(direct lookup) before falling back to pagination. - 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
Canonical response anchors
When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:
-
HIGH
-
P1
-
QE Debt
-
coverage_analysis_report.md
-
covered
-
Additional task-grounded exact anchors: zephyr-test-generation
When not to use it
- →Creating test cases
- →Manual coverage tracking
Prerequisites
Limitations
- →Analysis is read-only
How it compares
It provides a systematic, automated audit of test coverage and QE debt, rather than relying on manual spreadsheet tracking.
Compared to similar skills
quality-engineering-zephyr-coverage-analysis side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| quality-engineering-zephyr-coverage-analysis (this skill) | 0 | 2mo | No flags | Intermediate |
| python-testing-patterns | 77 | 2mo | Review | Intermediate |
| dependency-upgrade | 26 | 5mo | Review | Intermediate |
| test-cases | 57 | 7mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by HoangNguyen0403
View all by HoangNguyen0403 →You might also like
python-testing-patterns
wshobson
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
test-cases
cexll
This skill should be used when generating comprehensive test cases from PRD documents or user requirements. Triggers when users request test case generation, QA planning, test scenario creation, or need structured test documentation. Produces detailed test cases covering functional, edge case, error handling, and state transition scenarios.
backtesting-frameworks
wshobson
Build robust backtesting systems for trading strategies with proper handling of look-ahead bias, survivorship bias, and transaction costs. Use when developing trading algorithms, validating strategies, or building backtesting infrastructure.
reviewing-code
CaptainCrouton89
Systematically evaluate code changes for security, correctness, performance, and spec alignment. Use when reviewing PRs, assessing code quality, or verifying implementation against requirements.
wcag-audit-patterns
wshobson
Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns.