CtrlK
BlogDocsLog inGet started
Tessl Logo

analyzing-test-coverage

This skill analyzes code coverage metrics to identify untested code and generate comprehensive coverage reports. It is triggered when the user requests analysis of code coverage, identification of coverage gaps, or generation of coverage reports. The skill is best used to improve code quality by ensuring adequate test coverage and identifying areas for improvement. Use trigger terms like "analyze coverage", "code coverage report", "untested code", or the shortcut "cov".

86

1.01x
Quality

48%

Does it follow best practices?

Impact

90%

1.01x

Average score across 12 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./backups/skills-migration-20251108-070147/plugins/testing/test-coverage-analyzer/skills/test-coverage-analyzer/SKILL.md
SKILL.md
Quality
Evals
Security

Evaluation results

76%

1%

Coverage Analysis for a Node.js Utility Library

JavaScript coverage with nyc

Criteria
Without context
With context

Uses nyc

0%

0%

nyc in package.json

0%

0%

Coverage script added

37%

50%

Line coverage reported

100%

100%

Branch coverage reported

100%

100%

Function coverage reported

100%

100%

Statement coverage reported

100%

100%

Uncovered lines identified

100%

100%

Uncovered functions named

100%

100%

Coverage gaps addressed

100%

100%

Report file produced

100%

100%

100%

Identifying Test Coverage Gaps in a Python Text Processing Library

Python coverage with coverage.py

Criteria
Without context
With context

Uses coverage.py

100%

100%

Line coverage metric

100%

100%

Branch coverage metric

100%

100%

Function coverage identified

100%

100%

Statement coverage metric

100%

100%

Specific uncovered lines

100%

100%

Uncovered functions named

100%

100%

Uncovered branch identified

100%

100%

Report artifact produced

100%

100%

Coverage gaps addressed

100%

100%

61%

13%

Enforcing Test Coverage Standards in a Node.js Service

Coverage thresholds and CI/CD integration

Criteria
Without context
With context

Uses nyc for coverage

0%

0%

nyc in package.json devDeps

0%

0%

Coverage script in package.json

30%

30%

Line coverage threshold set

50%

50%

Branch coverage threshold set

50%

90%

Function coverage threshold set

50%

90%

Statement coverage threshold set

50%

90%

CI/CD pipeline includes coverage

100%

100%

Build fails on threshold breach

80%

90%

Report type configured

50%

50%

100%

Java Library Coverage Analysis

Java coverage with JaCoCo

Criteria
Without context
With context

Uses JaCoCo

100%

100%

JaCoCo in pom.xml

100%

100%

Line coverage reported

100%

100%

Branch coverage reported

100%

100%

Method/function coverage reported

100%

100%

Statement/instruction coverage reported

100%

100%

Uncovered lines identified

100%

100%

Uncovered methods named

100%

100%

Coverage gaps addressed

100%

100%

Report artifact produced

100%

100%

80%

Code Quality Audit for a Node.js Utility Library

Coverage and linting integration

Criteria
Without context
With context

Coverage tool used

0%

0%

Linting tool used

100%

100%

Both tools integrated

100%

100%

Line coverage reported

100%

100%

Branch coverage reported

100%

100%

Function coverage reported

100%

100%

Statement coverage reported

100%

100%

Linting issues reported

100%

100%

Uncovered code identified

100%

100%

Combined quality report

100%

100%

nyc configured in package.json

0%

0%

100%

Coverage Quality Gate for a Python Data Validation Library

Python coverage thresholds

Criteria
Without context
With context

Uses coverage.py

100%

100%

Minimum threshold defined

100%

100%

Branch coverage enabled

100%

100%

Line coverage reported

100%

100%

Branch coverage reported

100%

100%

Function coverage identified

100%

100%

Statement coverage reported

100%

100%

Specific uncovered lines

100%

100%

Uncovered function named

100%

100%

Failure on threshold breach

100%

100%

Report artifact produced

100%

100%

100%

TypeScript API Utilities: Coverage Analysis

TypeScript coverage with nyc

Criteria
Without context
With context

Uses nyc for coverage

100%

100%

nyc in package.json devDeps

100%

100%

Coverage script in package.json

100%

100%

Line coverage reported

100%

100%

Branch coverage reported

100%

100%

Function coverage reported

100%

100%

Statement coverage reported

100%

100%

Uncovered functions named

100%

100%

Specific uncovered lines

100%

100%

Report file produced

100%

100%

nyc configuration present

100%

100%

100%

Data Validation Library: Coverage Audit

Multi-module Python coverage gap analysis

Criteria
Without context
With context

Uses coverage.py

100%

100%

Branch coverage enabled

100%

100%

Line coverage per module

100%

100%

Branch coverage per module

100%

100%

Function coverage per module

100%

100%

Statement coverage per module

100%

100%

Uncovered lines identified

100%

100%

Uncovered functions named

100%

100%

Lowest coverage module identified

100%

100%

Report artifact produced

100%

100%

100%

Payment Processor: Automated Coverage Enforcement

Python coverage CI/CD gate

Criteria
Without context
With context

Uses coverage.py

100%

100%

Branch coverage enabled

100%

100%

Threshold defined in config

100%

100%

CI workflow file produced

100%

100%

CI runs coverage check

100%

100%

Build fails on breach

100%

100%

Line coverage reported

100%

100%

Branch coverage reported

100%

100%

Function coverage reported

100%

100%

Statement coverage reported

100%

100%

Specific uncovered lines

100%

100%

Uncovered function named

100%

100%

Repository
jeremylongshore/claude-code-plugins-plus-skills
Evaluated
Agent
Claude Code
Model
Claude Sonnet 4.6

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.