Receber por email
← Voltar para o catálogo

check-coverage

Comprehensive assessment of Unit / Integration / E2E three-layer test coverage, identify gaps and provide actionable recommendations.

172estrelas
Atualizado há 5 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add sd0xdev/sd0x-dev-flow

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/check-coverage/svg)](https://www.skillteca.com.br/skills/check-coverage)

Skills relacionadas

Ver todas de Desenvolvimento →

Alerta por categoria

Receba novas skills de Desenvolvimento toda segunda

1 email curto, só com as skills novas de Desenvolvimento. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Test Coverage Analysis

Trigger

  • Keywords: check coverage, test coverage, coverage analysis, coverage gaps, check-coverage

When NOT to Use

  • Test sufficiency review via Codex (use /codex-test-review)
  • Generating tests (use /codex-test-gen)
  • Running tests (use /verify)

Parent Skill Reference

See @skills/test-review/SKILL.md for Codex-based test review workflow.

Agent Dispatch

Agent({
  description: "Assess three-layer test coverage and identify gaps",
  subagent_type: "coverage-analyst",
  prompt: `Assess Unit / Integration / E2E test coverage for the feature docs at: $ARGUMENTS
Follow the steps defined in this skill.`
})

Task

Step 1: Read Feature Documentation

Read specified feature docs. Extract:

  • Feature name and objectives
  • Involved Service / Provider / Entity
  • Core flows and boundary conditions

Step 2: Identify Related Source Code

Search related source code based on feature documentation. Build source code inventory.

Step 3: Map Test Files

Check whether each source file has corresponding tests (unit, integration, e2e).

Step 4: Analyze Coverage Gaps

For each source file:

  1. Read source: Identify public methods, important branches, error handling
  2. Read tests: Identify covered cases
  3. Compare gaps: missing methods, uncovered branches, untested error scenarios

Step 5: Classify and Recommend

| Severity | Description | |----------|-------------| | 🔴 Critical | Core logic, data writes, amount calculations | | 🟠 Major | Important branches, error handling | | 🟡 Minor | Edge cases, utility functions | | ⚪ Nice-to-have | Logging, formatting |

Output

# Test Coverage Analysis Report

## Feature Overview
- Feature name: <from documentation>
- Documentation path: $ARGUMENTS
- Related modules: <list>

## Current Coverage
| Module | Source Path | Test Path | Coverage Status |
|--------|------------|-----------|----------------|

## Coverage Gaps
### 🔴 Critical
### 🟠 Major
### 🟡 Minor

## Recommended New Tests
| Priority | Test Type | Test Case | Target File |
|----------|-----------|-----------|-------------|

## Coverage Summary
| Metric | Status |
|--------|--------|
| Feature coverage | X/Y (Z%) |
| Happy path | ✅/❌ |
| Error path | ✅/❌ |
| Edge cases | ✅/❌ |
Compartilhar X LinkedIn