coverage-booster

Identify untested code paths and generate Jest or Vitest tests.

1|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/jieni777/opencode-config-backup --skill coverage-booster
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coverage-booster
Source: https://github.com/jieni777/opencode-config-backup/tree/main/skills/coverage-booster
Command: npx skills add https://github.com/jieni777/opencode-config-backup --skill coverage-booster

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Untested code paths cause silent bugs and undermine reliability; this tool automatically identifies missing tests and suggests or generates tests to fill coverage gaps.

Core Features & Use Cases

  • Detects untested functions, branches, and lines across a codebase
  • Generates Jest or Vitest compatible tests tailored to uncovered code
  • Prioritizes risky paths by complexity to maximize coverage efficiently

Quick Start

Run the tool on your project to auto-generate tests for uncovered areas.

Frequently Asked Questions about coverage-booster

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

FAQPage Schema
How do I auto-generate tests for untested TypeScript code paths?

It identifies untested functions, branches, and lines across your codebase, then generates ready-to-run Jest or Vitest compatible tests to fill those coverage gaps automatically.

Can I generate Jest or Vitest tests for specific files instead of the whole project?

You can apply this tool to entire directories or individual files, allowing you to prioritize risky code areas and generate tests specifically where coverage is needed most.

How does the tool decide which missing tests to generate first?

It evaluates untested code paths and prioritizes them by complexity, generating tests for the riskiest areas first to maximize coverage efficiency across the codebase.

Do I need to write manual test boilerplate when boosting code coverage?

No, you do not need manual boilerplate because the tool produces ready-to-run test files directly, allowing you to quickly fill coverage gaps in your JavaScript or TypeScript codebase.

What is the best way to find silent bugs caused by untested branches in JavaScript?

The best way is to detect untested functions and branches across your codebase, then auto-generate tailored Jest or Vitest tests to validate those specific missing paths and prevent silent bugs.