qa-coverage

Analyzes test coverage to identify untested code paths and missing test scenarios.

Updated Jul 13, 2026
One-click install
npx skills add https://github.com/torikhayes/aeai-dotnet-brownfield --skill qa-coverage-torikhayes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-coverage
Source: https://github.com/torikhayes/aeai-dotnet-brownfield/tree/main/.claude/skills/qa-coverage
Command: npx skills add https://github.com/torikhayes/aeai-dotnet-brownfield --skill qa-coverage-torikhayes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It helps teams find gaps in their test suites by identifying untested code paths, checking whether spec acceptance criteria are covered by tests, and assessing overall test coverage quality. ## Core Features & Use Cases - Untested Code Detection: Identifies code paths that lack test coverage so nothing critical ships unverified. - Acceptance Criteria Validation: Checks whether the acceptance criteria defined in a spec are actually covered by existing tests. - Missing Scenario Discovery: Finds missing test scenarios for a feature before release. - Use Case: Before merging a new checkout feature, run this Skill to confirm every acceptance criterion in the spec has a corresponding test and to surface edge cases that were never tested. ## Quick Start Ask the agent to analyze test coverage for the current feature and list any untested code paths or missing test scenarios.

Frequently Asked Questions about qa-coverage

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

FAQPage Schema
How do I find untested code paths in my project?▼

Invoke the qa-coverage skill, which loads the shared agent definition and runs a coverage analysis workflow. It scans the codebase for code paths lacking tests and reports the gaps it finds.

How to check if acceptance criteria are covered by tests?▼

The skill compares the acceptance criteria defined in a feature spec against the existing test suite. It reports which criteria have corresponding tests and which are missing coverage.

What does the qa-coverage skill actually do?▼

It reads the agent definition at .github/agents/qa-coverage.agent.md, which is the single source of truth shared with GitHub Copilot, then executes that coverage analysis workflow. The SKILL.md file itself contains no duplicated logic.

Can this skill write the missing tests for me?▼

The skill focuses on analysis: identifying untested paths, missing scenarios, and coverage quality. Writing the actual tests is a separate step you would perform after reviewing its findings.

When should I run a test coverage analysis?▼

Run it before merging a feature, after implementing new functionality, or when reviewing overall suite quality. It is most useful when a spec with acceptance criteria exists to validate against.