coverage-enhancer

Analyze existing test suites and source code to suggest additional unit tests that improve test coverage. Use this skill when working with test files and source code to identify untested code paths, missing edge cases, uncovered branches, untested error conditions, and gaps in test coverage. Supports major testing frameworks (pytest, Jest, JUnit, Go testing, etc.) and generates targeted test suggestions based on coverage analysis.

1.15x

Quality

73%

Does it follow best practices?

Impact

96%

1.15x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/coverage-enhancer/SKILL.md

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable with executable examples and tool commands, but the body is verbose and redundant, lacks a verify-and-re-measure feedback loop in its workflow, and points to reference files that are not bundled.

Suggestions

Collapse the redundant 'Coverage Analysis Patterns' and 'Common Coverage Gaps' sections and trim the 'Coverage Metrics' concept explanations that Claude already knows.

Add an explicit Step 6 verification checkpoint: run the suggested tests, confirm they pass, and re-run coverage to verify the gap actually closed before finalizing.

Either create the referenced references/*_coverage.md files or remove the dead links so navigation is honest.

Dimension	Reasoning	Score
Conciseness	Noticeably verbose: the 'Coverage Metrics' section explains basic concepts Claude already knows (line/branch/function/path coverage, '2^3 = 8 paths'), and 'Common Coverage Gaps' largely rehashes the five 'Coverage Analysis Patterns' that precede it.	2 / 5
Actionability	Provides copy-paste-ready executable test code, concrete per-language coverage commands (pytest --cov, npm test --coverage, mvn jacoco:report, go test -coverprofile), and a concrete test-suggestion template covering the common cases.	5 / 5
Workflow Clarity	Steps 1–5 are clearly sequenced, but there is no verification checkpoint (run the suggested tests, confirm they pass, re-measure coverage to confirm the gap closed); per the batch-operation cap, a test-generation workflow without that feedback loop cannot exceed 3.	3 / 5
Progressive Disclosure	Sections are headed and language-specific material is signaled via reference links, but the linked files (references/python_coverage.md, references/javascript_coverage.md, references/java_coverage.md, references/go_coverage.md) do not exist, and substantial inline content (five patterns, metrics, the full worked example) could live in separate files.	3 / 5
	Total	13 / 20 Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description with clear what/when structure and good trigger terms. Minor gaps in synonym coverage and the 'when' clause is slightly broad, leaving small overlap risk.

Suggestions

Add natural synonyms and file extensions to the trigger clause, e.g. 'code coverage', 'coverage reports', or framework-specific file names.

Tighten the 'when' trigger to the distinguishing intent (improving coverage on an existing suite) rather than the generic 'working with test files and source code'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Analyze existing test suites and source code', 'suggest additional unit tests', 'identify untested code paths, missing edge cases, uncovered branches, untested error conditions, and gaps in test coverage' — covering the task comprehensively.	5 / 5
Completeness	Explicitly answers both what ('Analyze existing test suites... suggest additional unit tests that improve test coverage') and when ('Use this skill when working with test files and source code to identify untested code paths...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms users would say ('test files', 'source code', 'unit tests', 'test coverage', 'pytest, Jest, JUnit, Go testing'), but omits common synonyms/extensions like 'code coverage', 'coverage report', or '.py'/.test files.	4 / 5
Distinctiveness Conflict Risk	The coverage-gap/test-suggestion niche is distinct, but the 'when working with test files and source code' trigger is broad and could overlap with general test-writing skills.	4 / 5
	Total	18 / 20 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (704 lines); consider splitting into references/ and linking	Warning
relative_links	Relative link issues: 4 missing	Warning
referenced_paths_exist	Referenced path issues: 8 missing	Warning

	Total	13 / 16 Passed

Repository: ArabelaTso/Skills-4-SE
Path: skills/coverage-enhancer/SKILL.md
Commit: 4f38503

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

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.