Skill

nightly-add-test-coverage

Nightly direct-execution skill for increasing test coverage. Receives pre-computed threshold data, writes tests targeting coverage gaps, updates thresholds, commits, and creates a PR.

Install

npx claudepluginhub codyswanngt/lisa --plugin lisa

Tool Access

This skill is limited to using the following tools:

EditMultiEditWriteReadGlobGrepBash

Preview

The caller provides pre-computed context:

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.2k

mcp-builder

9 files

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

anthropics-skills-13

124.2k

canvas-design

20 files

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

anthropics-skills-13

124.2k

Stats

Parent Repo Stars1

Parent Repo Forks2

Last CommitApr 6, 2026

Actions

View Source View Plugin View on GitHub View README

Nightly Test Coverage Improvement

The caller provides pre-computed context:

Package manager (npm, yarn, or bun)
Thresholds file path (vitest.thresholds.json or jest.thresholds.json)
Current thresholds (statements, branches, functions, lines percentages)
Proposed thresholds (each metric increased by the coverage increment, capped at 90%)
Metrics being bumped (which metrics are below target)

Instructions

Phase 1: Identify gaps

Run the project's coverage script with the provided package manager (e.g., npm run test:cov, yarn test:cov, or bun run test:cov) to get the coverage report -- identify gaps BEFORE reading any source files
Parse the coverage output to identify the specific files and lines with the lowest coverage. Prioritize files with the most uncovered lines/branches.
Read ONE existing test file to learn the project's testing patterns (mocks, imports, assertions). Do not read more than one.

Phase 2: Write tests incrementally — one file at a time

For each source file with low coverage (starting with the lowest):

Read only the uncovered sections of the source file using the coverage report line numbers -- do not explore the codebase broadly
Write a test file targeting the uncovered branches/lines for that source file
Run the test file in isolation (e.g., npx vitest run tests/my-new-test.test.ts) to verify it passes before moving on
If the test fails, fix it immediately. Do not move to the next file until the current test passes.
Repeat steps 4-7 for the next source file. Stop once you estimate the proposed thresholds will be met.

Phase 3: Verify and ship

Run the full coverage script to verify the new thresholds pass
Update the thresholds file with the proposed new threshold values
Re-run the coverage script to confirm the updated thresholds pass
Commit all changes (new tests + updated thresholds file) with conventional commit messages
Create a PR with gh pr create with a title like "test: increase test coverage: [metrics being bumped]" summarizing coverage improvements